Why a directory beats raw GitHub search
Type "mcp server" into GitHub search and you get tens of thousands of repositories ranked by stars or keyword relevance. Stars tell you very little: forks of abandoned projects keep their counts, new well-built servers start at zero, and the search index does not distinguish a production-grade connector from a weekend experiment with the same name.
A directory solves what raw search cannot. It groups repositories by what they actually are (MCP server, skill, subagent, hook, plugin), deduplicates forks, attaches metadata like license and last commit, and in the better cases gives you an install command you can paste instead of a README you have to decode.
The catch is that directories vary a lot in coverage, freshness and depth, and most cover only one slice of the Claude ecosystem. This guide compares the notable options as fairly as we can, including the cases where a competitor is the better pick.
What to judge a directory on
Coverage is the first question. Some directories list only MCP servers, others only skills. If your workflow mixes MCP servers with skills, subagents, hooks and plugins (and most Claude Code setups do), a single-category directory means juggling several tabs and several mental models.
Freshness and install experience come next. The ecosystem moves fast, repos get renamed, archived or abandoned, so check how often a directory re-crawls its sources. On install UX, the difference between a copy-paste command ('claude mcp add ...', a one-line skill install) and a bare GitHub link is several minutes per item, multiplied by everything you try.
Finally, safety signals and depth per page. Does the directory tell you whether a repo has a license, recent commits, a sane README? Does each item get its own page with configuration details, or just a name and a link? These signals matter more than they look: in ClaudeWave's audit of 2,006 MCP servers, 29% carried at least one security flag and 20% were unmaintained.
The MCP-only specialists: mcp.so, PulseMCP and MCP.Directory
mcp.so is the largest MCP-only directory and the obvious first stop if breadth within MCP is what you want. If a community MCP server exists, it is probably listed there, which makes it useful for finding long-tail connectors that smaller catalogs miss.
PulseMCP updates daily and adds something nobody else has: estimated usage data per server. When two servers do the same job (and in a pool of thousands, many do), an adoption signal is a practical way to break the tie. If you choose MCP servers by what other people actually run, PulseMCP is the right tool.
MCP.Directory is another solid MCP-only catalog and works fine as a second source. The shared limitation of all three is in the name: they cover MCP servers and nothing else. Skills, subagents, hooks and plugins, which together make up most of the installable Claude Code ecosystem, are out of scope. That is not a flaw if connectors are all you need; it just defines the job they are built for.
The skills-centric options: claudemarketplaces.com and skillsmp.com
claudemarketplaces.com covers skills, MCP servers and plugins, and its distinctive feature is editorial summaries: a human-written paragraph telling you what an item does and whether it is worth your time. In an ecosystem where most repos describe themselves badly or not at all, that editorial layer saves real reading time.
skillsmp.com focuses on skills and supports browsing in multiple languages, which makes it the most accessible option for people who prefer their own language. If your team works in Japanese or Portuguese, for example, it covers a need the English-first directories do not.
What both leave out is the rest of the picture. Subagents, hooks and templates are largely absent, and neither publishes security scoring on the repos they list. As skills-discovery tools they are good choices; as a single home for everything you install into Claude Code, they will leave gaps.
GitHub awesome lists: free and curated, but not browsable
The GitHub awesome lists (punkpeye/awesome-mcp-servers is the best known) are free, community-curated and genuinely useful. Every entry was added by a person who thought it was worth listing, and pull-request review acts as a light quality filter that pure crawlers do not have.
Their limits are structural rather than a question of effort. An awesome list is one long README: there is no search beyond Ctrl+F, no filtering by category or license, no per-item pages, no freshness checks on individual entries, and dead or renamed links can sit there for months until someone files a PR.
Use them the way they were designed to be used: as a curated reading list and a second opinion on what the community respects, not as a browsing or install tool. They pair well with any of the directories above.
ClaudeWave: what it does differently
ClaudeWave's bet is whole-ecosystem coverage in one place: 4,367 GitHub repositories spanning MCP servers (2,006 of them), tools, agents and subagents, skills, awesome lists, plugins, hooks and templates. On top of the repo index there is an item-level catalog of 12,118 installable items covering skills, subagents and slash commands, each with its own page and a one-command install.
The second difference is security. Every repo gets a Trust Score from 0 to 100 that combines maintenance status, fork ratio, license, owner reputation and README patterns with an AI review, refreshed every 12 hours. The same analysis produced 'The State of MCP Security 2026' report at /mcp-security: of the 2,006 MCP servers audited, 29% carry at least one security flag, 12% ship with no license and 20% are unmaintained.
ClaudeWave is also fully bilingual in English and Spanish, and keeps a model comparison chart that updates itself from Anthropic's API. To be fair about what it lacks: it has no usage estimates (PulseMCP does) and no human editorial summaries (claudemarketplaces.com does). If either of those signals is what you decide by, those sites serve it better.
Which directory for which job
If you only work with MCP servers, you do not need a whole-ecosystem directory. Use PulseMCP when adoption data should drive the choice between similar servers, and mcp.so when you want the widest possible MCP-only net, with MCP.Directory as a cross-check.
If skills are your focus, claudemarketplaces.com is the pick when you value a human summary before committing time to a repo, and skillsmp.com when you or your team browse better in a language other than English. The awesome lists remain the best quick answer to the question of what the community vouches for.
Choose ClaudeWave when you want everything (MCP servers, skills, subagents, hooks, plugins, templates) searchable in one place, when you care about security signals before installing third-party code, when you want one-command installs at the item level, or when you read in Spanish. In practice many people use two of these sites, and that is a reasonable outcome: they overlap less than it seems.