Six months ago, the problem was finding a good coding agent.
Today, the problem is starting to be something else.
Finding the right MCP server.
The ecosystem exploded.
There are already thousands of MCP servers for practically anything you can imagine:
- GitHub
- Jira
- Slack
- PostgreSQL
- Stripe
- Cloudflare
- Kubernetes
- Docker
- Notion
- Gmail
- Figma
- Playwright
- AWS
- Azure
And dozens more appear every week.
The consequence is pretty obvious.
Searching GitHub just isn’t enough anymore.
We need tools to help us discover what exists.
And that’s when specialized services start appearing to explore the MCP ecosystem.
Here are the four that are most worth knowing about.
1. MCP Compass
Best for: discovering MCP servers from your agent.
Repository:
MCP Compass works like a specialized search engine.
Instead of asking yourself:
“Does an MCP for Airtable exist?”
you can ask the agent directly:
“Find an MCP to manage Airtable.”
MCP Compass returns recommendations along with information about their capabilities.
Think of it as a search engine for MCP servers.
Instead of manually browsing GitHub.
Installation
Claude Desktop:
{
"mcpServers": {
"mcp-compass": {
"command": "npx",
"args": [
"-y",
"@liuyoshio/mcp-compass"
]
}
}
}
When to use it
When you’re not sure if an MCP already exists for the tool you need.
2. GitHub MCP Registry
GitHub maintains an official registry with hundreds of MCP servers published by the community.
It’s probably the best starting point when you want to discover new projects.
The advantages:
- official listing
- consistent metadata
- documentation
- installation
- active maintenance
In many cases you simply search by technology:
- postgres
- stripe
- github
- docker
and several implementations appear.
Great for browsing.
3. Smithery
Smithery is probably the most well-known marketplace in the MCP ecosystem today.
More than just a simple directory, it’s trying to become the “npm” of MCP servers.
You can:
- search for servers
- compare implementations
- install some directly
- discover new projects
Its catalog grows practically every week.
If you install MCPs regularly, it’s worth keeping among your favorites.
4. Awesome MCP Servers
Like any mature open source ecosystem…
an Awesome list appeared too.
And it remains an excellent way to discover projects.
The categories include:
- Databases
- Cloud
- Developer Tools
- AI
- Security
- Productivity
- Finance
- APIs
- Filesystems
It doesn’t have the experience of a marketplace.
But it does have a huge amount of useful links.
Which one to use?
Each one solves a different problem.
MCP Compass
When you’re already working with Claude and need to discover a server.
GitHub Registry
When you want to explore the official ecosystem.
Smithery
When you’re looking for a marketplace-like experience.
Awesome MCP
When you want to explore what the community is building.
A real example
Suppose you need to connect Claude Code with Cloudflare.
A year ago you probably would have done this:
Google
↓
GitHub
↓
README
↓
Install
Today the flow can be much simpler.
You ask the agent:
“I need to manage Workers and R2 from Claude Code. Is there an MCP for that?”
MCP Compass can suggest relevant servers.
If you want to compare alternatives, you open Smithery.
Then you verify the project in GitHub Registry.
And finally you install the one that best fits your case.
The entire process takes just a few minutes.
The real change
What’s interesting isn’t these tools.
What’s interesting is what they reveal.
Just a few months ago we had a handful of MCP servers.
Today the ecosystem is large enough to need:
- search engines,
- marketplaces,
- registries,
- curated lists,
- gateways,
- observability tools.
That’s usually a pretty clear signal.
A technology stops being experimental when tools start appearing to manage the ecosystem itself.
And I think that’s exactly what we’re seeing with MCP.
Servers are no longer a curiosity for enthusiasts.
They’re starting to become a platform.
Resources
MCP Compass
GitHub MCP Registry
Smithery
Awesome MCP Servers