There are over 12,000 MCP servers scattered across a dozen directories, registries, and GitHub lists. That volume is the problem. Searching one directory surfaces results another one misses. Picking the wrong starting point costs you time before you even evaluate a single server.
This is the navigation guide: every major discovery source, what it covers, what it misses, and which one to start with for your situation.
The Three Types of Discovery Source
Before listing anything, the distinction matters. Understanding the architecture behind MCP helps you judge which type of source fits your workflow.
Directories are human-browsable. You search or filter by category, language, or use case. Examples: PulseMCP, Smithery, Glama.
Registries are machine-readable and API-accessible. MCP clients use them to discover servers programmatically. Example: registry.modelcontextprotocol.io.
Meta-indexes aggregate multiple sources into one view. They do not host servers themselves. Example: automationswitch.com/mcp.
Most people need a directory. If you are building an MCP client or need the canonical list for programmatic access, use the official registry.
The Official Registry
registry.modelcontextprotocol.io is maintained by Anthropic with community contributions. It launched in preview in September 2025 and is the canonical source for client-side server discovery.
Best for: building an MCP client that needs programmatic server discovery, or verifying whether a server is in the canonical Anthropic-backed index.
For casual browsing, start with a directory instead. The registry is optimized for machine consumption, not editorial discovery.
The Major Directories
PulseMCP
pulsemcp.com. 11,840+ servers. Hand-reviewed daily by the founder since MCP's launch week.
Best for: quality-filtered discovery when you want reviewed servers with meaningful descriptions.
Smithery
smithery.ai. 7,000+ servers with a clean app-store interface, strong search, install commands, and hosted remote servers.
Best for: developers who want a clean install experience and broad coverage with one-click setup.
Glama
glama.ai/mcp/servers. 21,000+ servers and the largest volume directory in the ecosystem, with visual previews and daily updates.
Best for: maximum coverage when you want to see everything available, including niche and newly published servers.
MCP.so
mcp.so. 19,700+ community-submitted servers and strong coverage for third-party and unofficial tools.
Best for: finding community-built servers, especially newer or experimental ones.
| Criteria | PulseMCP | Smithery | Glama | MCP.so |
|---|---|---|---|---|
| Curation type | Hand-reviewed | Community + hosted | Automated + community | Community-submitted |
| Server count | 11,840+ | 7,000+ | 21,000+ | 19,700+ |
| Update cadence | Daily | Continuous | Daily | Continuous |
| Best for | Quality-filtered discovery | Install-ready browsing | Maximum coverage | Unofficial / third-party |
| Automation builder fit | ★★★★★ | ★★★★☆ | ★★★★☆ | ★★★☆☆ |
Additional Directories
mcp.directory
mcp.directory. 3,000+ servers and agent skills with one-click install for Cursor, VS Code, Claude Desktop, and ChatGPT.
Best for: IDE-first users who want to install directly from the listing page.
MCP Server Finder
mcpserverfinder.com. Curated directory with detailed server profiles, integration guides, compatibility info, and community ratings.
Best for: users who want implementation detail alongside discovery, with community reviews to help evaluate fit.
GitHub-Native Discovery
mcpservers.org mirrors the awesome-mcp-servers list and tracks 450+ curated servers.
github.com/modelcontextprotocol/servers is the official reference implementation repository from Anthropic and the authoritative source for first-party servers.
GitHub-native sources are reliable if you already trust repository stars, release hygiene, and maintainer activity as quality signals.
Leaderboards and Trending
mcpmarket.com publishes daily rankings by community engagement and a top-100 leaderboard by GitHub stars.
Leaderboards bias toward developer tools with GitHub presence. Automation-focused servers may score lower because their users are not starring repositories. Do not use trending as a proxy for fit.
The Meta-Index
Automation Switch MCP index aggregates 18+ directories, registries, and indexes into one view. Each source is described, categorized, and linked directly.
It is useful when you do not yet know which directory to search, or when you want to compare discovery sources before leaving the site.
Which One to Use: Decision Framework
| Criteria | Start here | Escalate to |
|---|---|---|
| Browse and discover | Smithery or Glama | PulseMCP for quality filter |
| Curated, quality-only | PulseMCP | Official registry for canonical check |
| Building an MCP client | Official registry API | GitHub reference implementations |
| Community or unofficial servers | MCP.so | mcpservers.org |
| Install from my IDE | mcp.directory | Smithery for broader coverage |
| I do not know where to start | automationswitch.com/mcp | Whichever directory fits your need |
| I want what is trending | mcpmarket.com leaderboard | Reddit r/mcp |
Conclusion
Directories are for browsing. Registries are for building. Meta-indexes are for navigation.
The MCP discovery ecosystem is fragmented by design. Different sources serve different needs, and the right answer depends on what you are trying to do. Start with the source type that matches your situation, then escalate if the first result does not surface what you need.
