MCP ecosystem tops 13,000 servers as monthly SDK downloads hit 97 million

Ecosystem growth by the numbers

A community analysis published on dev.to on August 25, 2026 tallies the size of the Model Context Protocol (MCP) ecosystem and finds it scaling quickly. According to the post, there were more than 13,000 MCP servers listed across npm and GitHub as of May 2026. Monthly downloads of MCP SDKs have reached 97 million, roughly triple the figure from six months earlier, and new server registrations grew 400% year over year.

Demand is not evenly distributed. Anthropic's official reference servers remain among the most-pulled packages, with the filesystem server alone accounting for about 48,500 downloads per month, according to the post.

One caveat worth noting: these figures come from a single developer's review of public registries rather than an official audit, so they are best read as directional indicators of growth rather than a precise census.

From protocol to default

The author's central claim is that MCP has crossed over from being one option among several to the default plumbing for agent tool use. In the post's framing, MCP is on its way to becoming the standard method for connecting AI models to external systems such as databases, APIs and file systems, rather than a specification that merely exists.

The growth pattern is consistent with that reading. SDK downloads tripling in six months suggests builders are embedding MCP clients and servers into shipping products rather than running experiments, and server registrations climbing 400% year over year indicates supply is keeping pace with demand from agent hosts.

Discovery is the remaining gap

For all the growth, the post identifies discovery as the ecosystem's weak point. Finding the right MCP server still tends to mean trial-and-error keyword searches on npm or manual digging through GitHub repositories, with no canonical directory in between. The practical effect is that an ecosystem of 13,000 servers feels much smaller to any individual developer, because relevance depends on search luck.

A registry attempt: mcp-hub

Alongside the analysis, the author shipped a small CLI aimed at that gap. mcp-hub installs globally via npm and provides search and install commands — for example, looking up a database server and installing the official Postgres package from within the tool. It is early-stage: the post describes six commands, five official servers in the registry, and packages verified against npm. The roadmap lists private registries aimed at enterprise teams, community submissions through GitHub issues, and CI/CD hooks for auto-publishing servers.

Why it matters

If the numbers are even roughly accurate, agent-tool integration is consolidating around a single protocol at unusual speed. That has two consequences. First, tool builders get a distribution multiplier: an MCP server written once can be consumed by any compatible agent host. Second, the ecosystem's bottleneck shifts from protocol adoption to plumbing — registries, package verification, and enterprise controls such as private registries and automated publishing pipelines.

The gap the dev.to author highlights, and tries to narrow with mcp-hub, is precisely the kind of infrastructure that becomes contested once a standard wins. For teams building agents, MCP support is increasingly table stakes; for the wider ecosystem, the next battles look set to be fought over discovery and trust rather than the protocol itself.