OLKERIAI News
← All AI news
OLKERI · AI NEWS
ResearchGlobal2 September 20262 min read

By Olkeri.space

Anthropic's connector protocol passes 400 million monthly downloads

MCP's SDK downloads have roughly quadrupled in a year, and its latest specification rebuilds the core as stateless — the unglamorous change that says agents have moved from demos to deployments.

Read this story in: Français · Deutsch · Español

The Model Context Protocol, Anthropic's open standard for connecting AI systems to tools and data, has passed 400 million monthly SDK downloads, according to reporting by 36Kr — roughly a fourfold increase in a year, from about 97 million in March. The milestone follows the protocol's largest specification revision, published in late July, which moves the core to a stateless architecture and adds standardised extensions aimed at enterprise deployment.

Download counts flatter every project that publishes them: they include CI systems and transitive installs, and they are not a count of users. But a fourfold move in a year is directional evidence of something protocols rarely achieve, which is escape velocity. Connector standards fail by default, because every platform prefers its own. MCP's unusual outcome is adoption across competing labs and vendors — the one property a connector standard actually needs.

The stateless-core change is the substantive news inside the boring number. A protocol whose sessions carry state is pleasant for demos and hostile to production: every long-lived connection pins a server, complicates failover and caps horizontal scale. Rebuilding around stateless operation is what a standard does when its users stop being hobbyists wiring up a laptop and start being enterprises running fleets. The revision describes, more credibly than any announcement could, where agent deployments actually are.

The governance question grows with the numbers. A protocol authored by one lab and adopted by an industry sits in an odd position: the value accrues to everyone, but the pen stays in one hand. Web standards resolved this with consortia; container standards with foundations. If MCP's trajectory continues, pressure for a neutral home for the specification will follow it — not because the current stewardship has misbehaved, but because infrastructure this widely depended on eventually gets asked to prove it belongs to no one.