MCP stories from the field

In the ongoing debate about the Model Context Protocol (MCP) versus direct API calls and CLIs, the recent decision by Perplexity to drop MCP in favor of direct APIs has reignited discussions within the tech community. While some leaders in the field criticize MCP, arguing for the simplicity of APIs, large organizations and security-focused entities emphasize the importance of MCP for maintaining security, governance, and control. Companies like Stripe have developed sophisticated internal infrastructures, such as their Toolshed layer, to manage MCPs effectively, providing a curated and secure environment for tool usage. Meanwhile, other companies are exploring different approaches, such as democratizing MCP creation internally or developing MCP routers to simplify tool accessibility. Despite differing opinions, what's evident is the lack of consensus and the potential market opportunity for structured solutions to manage MCPs and context layers at scale. As the debate continues, many enterprises remain heavily reliant on MCPs, underscoring the gap between industry practices and the views of some tech influencers.