Featured image of post Will MCP Fail? Questions About MCP

Will MCP Fail? Questions About MCP

Doubts About the Value of MCP

Model-Context Protocol (MCP has attracted widespread attention and rapid adoption since its launch. A large number of AI tools now support MCP. (For a detailed introduction to MCP, see my previous article【】) But as MCP has risen to prominence, doubts about it have gradually begun to emerge—for example, concerns about its security limitations (see my previous article【】). Recently, Edgenesis founder Yongli, Chen also published an article arguing that MCP is destined to fail. Here I have organized his main points into this article (see the link at the end for the original), so that you may use them as a reference and form your own judgment.

Introduction

Model-Context Protocol (MCP) has been in the spotlight since its very inception. It has been hailed as a universal standard aimed at seamless integration between artificial intelligence (AI) models and all kinds of software tools. On the surface, the protocol does address a genuine industry pain point: replacing today’s chaotic jumble of custom application programming interfaces (APIs) and proprietary plugins with one simple, standard solution. MCP’s proponents paint a future in which AI agents can effortlessly connect to countless applications without tedious custom integration.

Yet for all its technical elegance and the enormous attention it drew early on, MCP is destined to struggle. This is not due to any technical defect, but because it fundamentally misunderstands a crucial economic reality: in the digital business landscape, end-user attention is the key to commercial success.

Every company will go to great lengths to guard user attention, because it is their primary source of monetization. Tool vendors therefore simply cannot afford the price of reducing themselves to mere backend functions by adopting MCP across the board.

The Real Battleground - Ownership of Attention

To understand why MCP faces resistance, we must first consider a basic fact: whoever controls the user interface controls the user relationship. A company that owns the interface thereby owns user engagement, data, and the revenue opportunities that arise from them. Services relegated to the backend, by contrast, become freely replaceable commodities—not only easy to substitute, but also stripped of any direct contact with their customers.

History has repeatedly proved this law. Facebook, for example, built its business empire precisely by turning third-party applications into pure content providers. The early social-gaming giant Zynga learned this lesson the hard way. When Facebook changed its platform rules and tightened restrictions, the visibility of Zynga’s games plummeted. Zynga’s fate was sealed, because Facebook held a firm grip on user attention and thus dictated Zynga’s revenue and customer interaction.

Similarly, Twitter blocked third-party clients because these clients allowed users to bypass Twitter’s advertising system, which amounted to “stealing” the platform’s user attention. Apple’s attitude toward web apps is another highly persuasive example: for years, Apple deliberately limited the functionality of web apps on iOS to ensure that native apps in the App Store stayed dominant, thereby preserving Apple’s direct relationship with users and its revenue streams.

MCP’s Naive Proposal

MCP is, in effect, asking software vendors to voluntarily accept a new model: turning their core functionality into simple backend services accessed primarily through AI-driven interfaces.

Imagine a future in which booking a trip is done entirely through an AI assistant that interacts invisibly behind the scenes with airlines, hotels, and travel agencies via MCP. In this model, the interface—the point of user contact and decision-making—belongs entirely to the AI assistant, leaving the vendors unable to reach user attention directly.

This effectively demotes vendors from “destinations” with differentiated brands and customer loyalty to standardized “utilities.” Such a shift would seriously threaten the core ability of vendors to capture value.

Software-as-a-Service (SaaS) and tool vendors rely heavily on direct interaction with users to monetize their businesses—for example, upselling value-added features, crafting branded experiences, and collecting valuable user data.

Once they fully embrace MCP, these vendors hand the user interface over to external AI aggregators, inevitably losing their customer relationships and direct monetization channels.

Evidence from the Current AI Ecosystem

In reality, major software companies have behaved very cautiously in handling their relationships with AI-driven platforms such as OpenAI’s ChatGPT and Anthropic’s Claude.

Whether Salesforce, Microsoft, or Google, all of them are seeking to embed AI capabilities deeply into their own proprietary interfaces, rather than allowing their tools to be fully invoked by external AI agents.

For example, Einstein GPT from Salesforce integrates AI directly into its customer relationship management (CRM) system, locking users firmly inside its own ecosystem. Similarly, Microsoft has prioritized deeply embedding Copilot AI into the Office and Windows environments. When tool vendors do attempt external AI integration, they usually provide only limited functionality—enough to attract users, but not enough to fully replace their own interfaces. A travel app, for instance, might let an AI assistant browse flight information, but will ultimately steer users back to its own platform to complete the booking, so as to preserve the crucial customer interaction and upselling opportunity.

MCP Is Bound to Face Difficulties

Past experience clearly reveals why MCP has struggled to gain widespread adoption—especially since the large software vendors that dominate market attention could never pivot fully to MCP.

If these vendors truly believed it was worthwhile to give up user attention in exchange for open integration, they would have long since offered fully featured public APIs for free. The opposite is true: they typically build tightly controlled ecosystems, attracting new users through selective integration, and would never voluntarily surrender control over the user experience or revenue.

This careful balancing act highlights MCP’s fundamental flaw: no matter how elegant or superior a protocol may be on the technical side, software vendors have no incentive to hand their precious customer relationships and monetization capabilities over to external aggregators.

Platform Economics Is the Foundation of Technology

Ultimately, what decides MCP’s fate is not its technical merits or demerits, but commercial incentives and the dynamics of platform economics. Platform owners will inevitably find ways to protect their core asset—the direct connection with users. The approach MCP proposes fundamentally upends this dynamic, setting it against deeply entrenched economic incentives.

In practice, MCP may gain limited adoption among some smaller vendors or niche communities where openness itself has intrinsic value. Among the mainstream SaaS vendors and large platforms that dominate today’s digital economy, however, adopting MCP is at best more about extending one’s own reach than exposing one’s own capabilities.

In essence, although MCP aspires to become a universal standard, it faces a harsh economic reality: no company wants to resign itself to becoming an invisible backdrop. Every company will fight tooth and nail to defend its control over the user interface (that is, control of the user relationship) and to limit any integration that might threaten its strategic position.

Conclusion

The vision of seamless, universal AI integration painted by MCP is undeniably compelling, but in the business world, striking technology alone rarely decides success or failure.

The battle over standards is ultimately a battle over economic power. MCP’s design challenges the very incentive structures that have driven the digital economy for decades. It is precisely for this reason that MCP faces enormous obstacles on the road to widespread adoption.

Until it can better align with platform economics and vendors’ inherent incentives, MCP’s ambition to become the universal standard for AI-tool integration is likely to remain a distant dream.

Original article link: https://www.forbes.com/councils/forbestechcouncil/2025/06/12/mcp-will-fail-and-heres-why/

Built with Hugo
Theme Stack designed by Jimmy