MCP SDK downloads triple to 97 million a month as server count passes 13,000

Headline numbers

A community analysis published on dev.to on 28 August 2026 puts the Model Context Protocol (MCP) ecosystem at 97 million SDK downloads per month, a figure the author says is triple the level of six months earlier. The post also counts more than 13,000 MCP servers spread across npm and GitHub as of May 2026.

Two further data points stand out. New server registrations are reported to have grown 400% year over year, and Anthropic's official reference servers draw real traffic in their own right, with the filesystem server alone accounting for roughly 48,500 downloads a month.

These are numbers one developer compiled through their own digging rather than official statistics from Anthropic or npm, so they are best treated as directional indicators rather than audited figures.

From protocol to plumbing

The author's core argument is that MCP has stopped being merely a specification and is becoming the default wiring that connects AI models to external systems: databases, APIs, file systems and more. The download and registration figures are offered as evidence. Developers are installing SDKs and publishing servers at a pace that suggests one-off, bespoke tool integrations are giving way to integrations built against a shared standard.

Discovery is now the bottleneck

Even with that growth, the post identifies a persistent gap: finding the right server. There is no dominant index, so developers either guess at search terms on npm or dig through GitHub repositories. In an ecosystem listing thousands of servers, that friction matters far more than it did when the catalogue was small. The harder problem has shifted from building servers to locating and evaluating them.

A community-built registry

The author's response is mcp-hub, a command-line tool installable from npm. It wraps search and install into short commands: install the tool globally, search for a category such as databases, and add a server like the official Postgres one in a couple of steps. The initial registry ships with five official servers, each verified as a real npm package.

The stated roadmap covers private registries for enterprise teams, community submissions through GitHub issues, and CI/CD integration so that MCP servers publish automatically as part of a pipeline.

Why it matters

If the growth numbers are even roughly right, MCP is moving from a protocol proposed by a single lab toward shared infrastructure for agent tooling. Monthly SDK downloads tripling inside half a year means integrations increasingly get built once, against a standard, instead of once per model and per tool, which is precisely the cost saving a protocol is supposed to deliver.

The consequence is that the ecosystem's constraint is migrating. The open question is no longer only whether the standard will be adopted, but whether developers can find, vet and govern the servers they connect their agents to. That is why registry tooling such as mcp-hub is starting to appear, and why discovery, verification and enterprise controls look like the next competitive layer built on top of the protocol itself.