MCP protocol gaining traction

A year ago, giving an artificial intelligence assistant access to GitHub, Slack, or a database usually meant building a custom connector for each app. The Model Context Protocol was released by Anthropic on November 25, 2024 to replace that one-off work with a shared standard. (anthropic.com) Think of it like the difference between every phone maker inventing its own charger and everyone settling on one plug. The official specification says one protocol can expose tools, prompts, and resources to many artificial intelligence apps through the same interface. (modelcontextprotocol.io) The basic layout is simple. A host app like a chat client or code editor opens a connection, and a server on your machine or on the web offers actions the model can take and data it can read. (modelcontextprotocol.io) That matters because the old math was ugly. Anthropic’s launch post described the problem as fragmented integrations, where every new data source needed its own custom implementation, which made connected systems hard to scale. (anthropic.com) The new part is not just the protocol on paper. Claude’s documentation now treats Model Context Protocol as the system behind its connectors, and it spells out concrete guardrails like per-connector authentication, user control, and tool labels for read-only or destructive actions. (claude.com) Cursor has also made Model Context Protocol a first-class feature in its editor. Its documentation says developers can connect external tools and data sources, install servers, configure authentication, and wire in databases, application programming interfaces, and third-party services. (cursor.com) Zed is using the same standard in a slightly different way. Zed’s docs say it supports the protocol’s tools and prompts features, lets people add local command-based servers or remote web-based servers, and can even refresh the tool list when a server changes at runtime. (zed.dev) Windsurf has pushed it even closer to a storefront. Its docs describe an MCP Marketplace inside Cascade, blue checkmarks for official servers, support for standard input and output, Streamable Hypertext Transfer Protocol, and Server-Sent Events, plus a hard cap of 100 enabled tools at one time. (docs.windsurf.com) That is why people are starting to talk about protocol support as distribution, not plumbing. If one server can be installed inside Claude Desktop, Cursor, Zed, and Windsurf, the developer who builds that server is no longer pitching one app at a time. (claude.com) (cursor.com) (zed.dev) (docs.windsurf.com) Anthropic has been sanding down the rough edges that kept this from spreading beyond power users. On June 26, 2025 it introduced Claude Desktop Extensions, later renamed with the.mcpb file extension on September 11, 2025, so a local server could be bundled into one installable package instead of requiring Node.js, manual JSON edits, and dependency wrangling. (anthropic.com) The ecosystem is also behaving like a real standard now, not a side project. The main specification repository on GitHub showed about 7,800 stars when checked this week, and the docs site now presents multiple dated spec versions, which is what mature protocols do when different clients adopt features at different speeds. (github.com) (modelcontextprotocol.io) There is still a catch. The official specification spends a full section on security and says users must explicitly consent to data access and actions, because a protocol that can read files, call services, and execute tools is useful for coding help and risky for the exact same reason. (modelcontextprotocol.io) So the story is not that Model Context Protocol has already won. The story is that once Claude Desktop, Cursor, Zed, and Windsurf all decide the same interface is worth supporting, a boring technical standard starts to look a lot like shelf space. (anthropic.com) (claude.com) (cursor.com) (zed.dev) (docs.windsurf.com)