MCP hit 13,000+ servers and 97M monthly SDK downloads. mcp-hub solves discovery with search and install commands. Install it now to stop guessing on npm.
Key Takeaways
- MCP hit 13,000+ servers and 97M monthly SDK downloads.
- mcp-hub solves discovery with search and install commands.
- Install it now to stop guessing on npm.
The MCP Ecosystem Has Exploded — Discovery Hasn't Caught Up
The numbers are staggering. As of May 2026, there are 13,000+ MCP servers on npm and GitHub. Monthly SDK downloads hit 97 million — triple what they were just six months ago. New server registrations are growing 400% year-over-year. Anthropic's official filesystem server alone pulls 48,500 downloads per month.
MCP isn't a niche protocol anymore. It's the standard way to give Claude Code access to databases, APIs, file systems, and everything else. But here's the problem: finding the right server is still a guessing game.
The Discovery Gap
If you've tried to add an MCP server to Claude Code, you know the pain. You search npm with vague terms, hoping the package name matches what you need. You dig through GitHub folders, checking star counts and last commit dates. It's slow, error-prone, and wastes time you could spend actually building.
That's the gap developer GrahamduesCN set out to fix with mcp-hub — a CLI tool that brings sanity to MCP server discovery.
What mcp-hub Does
Install it globally, then search and install from your terminal:
npm install -g mcp-hub
mcp-hub search database
mcp-hub install @modelcontextprotocol/server-postgres
Six commands total. Five official servers already in the registry. Every package is real and verified on npm — no squatting, no abandoned repos, no dead ends.
Why This Matters for Claude Code Users
Every MCP server you add to Claude Code consumes context window when it loads its tools. The community has been shifting toward MCP minimalism — preferring fewer, higher-quality servers to reduce context bloat (we covered this trend on July 28).
That makes discovery even more critical. You can't afford to install five random servers hoping one works. You need to find the right one quickly, verify it's maintained, and move on.
mcp-hub addresses exactly that workflow: search, verify, install, done.
Try It Now
- Install mcp-hub:
npm install -g mcp-hub - Search for what you need:
mcp-hub search database - Install the verified server:
mcp-hub install @modelcontextprotocol/server-postgres - Add it to your Claude Code config and start using it
The tool is open-source on GitHub (GrahamduesCN/mcp-platform).
What's Next
The roadmap includes private registries for enterprise teams, community submissions via GitHub issues, and CI/CD integration for auto-publishing MCP servers. If you've built a server worth sharing, that's the channel to get it discovered.
The Bottom Line
The MCP ecosystem is growing faster than anyone can track manually. Tools like mcp-hub are the first step toward making that growth usable. Install it, find the servers you actually need, and stop wasting time on discovery.
Your context window will thank you.
Source: dev.to
[Updated 02 Aug via simon_willison]
The MCP ecosystem just took a major leap forward with the release of MCP 2.0, a stateless specification that simplifies client and server implementation. Simon Willison, a prominent developer, built three tools this week to explore the new protocol, including mcp-explorer, a CLI for probing MCP servers without installation. The new spec eliminates the need for session IDs, using a single HTTP request instead of two, making it easier to build scalable web applications. This shift could accelerate adoption beyond the existing 13,000+ servers, as smaller models can now drive MCP tools more effectively, reducing reliance on risky shell environments.
Originally published on gentic.news
Top comments (0)