We know this firsthand. We built the Dyno Mapper MCP server — available now on npm as @dynomapper/mcp-server — and went through every one of these directories ourselves. This list comes from direct experience, not theory.

Below is every major MCP server directory, registry, and listing platform worth your time. For each one, you’ll know what it is, who uses it, and how to get listed.

Bookmark this. Come back when new directories pop up. This list gets updated.

Why Distribution Matters for MCP Servers

Think about npm. Or Hugging Face. The reason developers trust those ecosystems isn’t just the quality of individual packages. It’s that they have central places to discover things.

MCP is in the middle of that same transition right now. The protocol got widespread adoption fast. The directory ecosystem is still catching up. That means early listings carry serious weight. Getting into these directories while they’re still growing gives you compounding exposure.

The Dyno Mapper MCP server connects AI agents directly to Dyno Mapper’s sitemap and content inventory platform — letting tools like Claude Desktop and Cursor crawl, audit, and map website structure without leaving the chat. Getting that server discovered meant going through every directory on this list. Now you don’t have to figure it out yourself.

Don’t wait.

The Official Registry

1. Model Context Protocol Official Registry

URL: registry.modelcontextprotocol.io
Maintained by: Anthropic / MCP Steering Group

This is the source of truth. The canonical registry maintained by the people who built the protocol.

If you’re only listing in one place, it’s this one. When AI clients like Claude Desktop, Cursor, and others look for verified servers, this is where the chain of trust starts.

Getting listed here signals legitimacy. It’s a quality bar, not an open dumping ground. Your server needs to be real, functional, and documented.

The GitHub repo at github.com/modelcontextprotocol/servers is the companion to the registry. It houses reference implementations and community submissions. A PR to that repo is the path to getting indexed.

How to submit: Open a PR or issue on the official GitHub repo. Follow the contribution guidelines. Make sure your server has proper documentation.

The Power Players

2. Smithery

URL: smithery.ai
Server count: 6,000+

Smithery acts as an index for helping you discover, install, and manage MCP servers. Think of it as the npm registry but built specifically for the MCP ecosystem.

Smithery is quickly becoming to MCPs what Hugging Face is to ML models. Developers come here first when they’re looking for a server to solve a specific problem.

What makes Smithery different from a simple list is its CLI. You can publish your MCP server URL directly via smithery mcp publish, and it becomes instantly discoverable and installable by anyone running the Smithery CLI. One command gets your server in front of thousands of developers.

The platform supports both hosted and local deployment modes, which means your listing can serve two audiences at once.

How to submit: Use the Smithery CLI: smithery mcp publish "https://your-server.com" -n yourorg/your-server. Or submit via the web dashboard at smithery.ai.

3. Glama

URL: glama.ai/mcp
Server count: 21,500+

Glama indexes 21,586 MCP servers, updated daily, and proxies 2,223 connectors through its gateway with full call logging, per-tool access control, and managed OAuth.

Glama is for the serious infrastructure crowd. It’s not just a directory. It’s a registry with a built-in inspector, security scanning, and an API gateway. Developers who need observability and access control land here.

Getting listed on Glama also means your server appears in their tool search. Users can search across tools from every MCP server to find the exact capability they need. That’s a different discovery path than browsing a category list.

How to submit: Glama auto-indexes open-source MCP servers from GitHub. For claiming or managing your listing, check their docs at glama.ai.

4. MCP.so

URL: mcp.so
Server count: 20,000+

MCP.so is a third-party MCP Marketplace with over 20,000 MCP servers collected. It’s one of the largest aggregators in the space.

The audience here skews toward developers looking for quick discovery and integration options. The platform includes a playground and a blog, which means there’s content traffic coming in from search, not just direct navigation.

How to submit: Click the Submit button on mcp.so or go directly to their GitHub issues page.

5. PulseMCP

URL: pulsemcp.com
Server count: 12,650+

PulseMCP tracks estimated weekly visitor counts for each server, which is a unique data point you won’t find in most other directories. That visitor data matters. It tells you which servers are actually getting traction, and it means your listing comes with built-in social proof over time.

PulseMCP also has filtering by official vs. community classification and sorting by recommendation, recency, and popularity. That organization helps your server surface to the right searchers.

How to submit: Use the Submit button in the navigation bar at pulsemcp.com.

Community Directories

6. Awesome MCP Servers (punkpeye)

URL: mcpservers.org
GitHub: github.com/punkpeye/awesome-mcp-servers

This curated list covers an enormous range of categories from browser automation to academic citation tools. It’s maintained by Frank Fiegel and has strong community engagement.

“Awesome” lists carry a lot of weight in developer circles. A listing here drives GitHub traffic and signals that real humans vetted your project. That’s different from being indexed by a crawler.

How to submit: Open a PR on the GitHub repo. Your server needs a README, clear description, and working installation instructions.

7. Awesome MCP Servers (wong2)

URL: github.com/wong2/awesome-mcp-servers

Another well-maintained curated list. It’s cross-referenced in the official Anthropic GitHub repo, which gives it extra visibility.

Don’t skip this one just because you submitted to the punkpeye list. Different maintainers, different audiences, different search footprint.

How to submit: PR on the GitHub repo. Include a clear one-line description and a link to your repo.

8. Awesome MCP Servers (appcypher)

URL: github.com/appcypher/awesome-mcp-servers

Maintained by Stephen Akinyemi. Part of the broader “awesome list” network that gets indexed, shared, and referenced across developer communities.

Multiple “awesome” list entries compound. Each one is a backlink. Each one is a new surface for discovery.

How to submit: GitHub PR.

9. MCP Server Finder

URL: mcpserverfinder.com

MCP Server Finder positions itself as the definitive resource for discovering, comparing, and implementing MCP servers — with detailed profiles including implementation guides, compatibility information, and real-world use cases.

The site targets both developers and enterprises, which is a broader audience than most directories. If you’re building something with an enterprise use case, this listing matters.

How to submit: Submit through the site’s submission form at mcpserverfinder.com.

10. MCP Hunt

URL: mcphunt.com

MCP Hunt is a realtime platform for discovering trending MCP servers with momentum tracking, upvoting, and community discussions. Think Product Hunt meets Reddit, but for MCP.

The community voting mechanic matters here. If your server launches and gets traction on MCP Hunt, that momentum gets amplified. It’s a different acquisition channel than passive indexing.

How to submit: Submit your server for a launch at mcphunt.com. Coordinate with your community for upvotes on launch day.

11. MCP.ing

URL: mcp.ing

MCP.ing is a community-focused list of MCP services with a convenient search function. Smaller than the power players, but active enough to be worth a listing.

The search-first interface means keyword optimization in your title and description matters more here than anywhere else on this list.

How to submit: Check the site for submission instructions at mcp.ing.

12. AIBase MCP Directory

URL: mcp.aibase.com

AIBase maintains a continuously updated curated list of MCP servers covering multiple categories including browser control, cloud platforms, databases, developer tools, file systems, finance, and utilities — with GitHub stars listed alongside each entry.

The star count display is useful social proof. New visitors immediately see which servers have community trust behind them.

How to submit: Submit through the AIBase platform at mcp.aibase.com.

GitHub-Based Resources

13. Official MCP GitHub Repository

URL: github.com/modelcontextprotocol/servers

This is the official GitHub repository with the reference implementations maintained by the MCP steering group.

A listing here isn’t just exposure. It’s credibility. The repo carries weight because it’s directly maintained by the team that owns the protocol spec.

How to submit: Open a PR adding your server to the community listings section of the README.

14. Best of MCP Servers

URL: github.com/tolkonepiu/best-of-mcp-servers

A ranked list of MCP servers updated weekly. The “best-of” framework scores projects based on GitHub activity, stars, and other signals. Rankings update automatically.

This is a long-game listing. As your server grows its GitHub presence, your rank improves without you doing anything extra.

How to submit: Submit via a PR to the projects.yaml config file in the repo.

15. mkinf Registry

URL: mkinf.io

mkinf is an open-source registry of hosted MCP servers to accelerate AI agent workflows. It focuses on hosted servers specifically, which makes it relevant if you’re running your server as a managed service rather than a self-install package.

How to submit: Check the mkinf GitHub repo and docs at mkinf.io for submission instructions.

16. OpenTools

URL: opentools.ai

OpenTools is an open registry for finding, installing, and building with MCP servers. Developer-focused with an emphasis on tool discovery by capability.

How to submit: Submit via their registry process at opentools.ai.

Niche and Emerging Directories

17. Awesome Remote MCP Servers

URL: github.com/JAW9C/awesome-remote-mcp-servers

This curated list focuses specifically on remote MCP servers, including their authentication support.

If your server is remote and uses OAuth or API key auth, this list is more relevant than a general directory. Niche listings convert better because the audience has exactly the intent you need.

How to submit: GitHub PR.

18. Awesome Crypto MCP Servers

URL: github.com/badkk/awesome-crypto-mcp-servers

If your server is crypto or DeFi-focused, this is your vertical directory. Don’t sleep on niche listings. The people browsing a crypto-specific list have higher intent than someone scrolling a general directory.

How to submit: GitHub PR.

Don’t Forget npm

If your MCP server is published as an npm package, the package page itself is a discovery surface. Developers search npm directly when they know what they’re looking for.

Make sure your package.json keywords are doing work:

"keywords": ["mcp", "mcp-server", "model-context-protocol", "claude", "cursor", "ai-tools"]

The Dyno Mapper MCP server is a good example of how to structure an MCP package page — clear description, install command front and center, and keywords that match how developers search.

The Submission Checklist

Before you submit anywhere, make sure you have these ready. Incomplete listings get ignored or rejected.

Your README needs:

• Clear one-line description of what the server does
• Installation instructions (preferably with copy-paste commands)
• Configuration options and environment variables documented
• At least one usage example
• License file

Your server needs:

• A public GitHub repo or npm package (like npmjs.com/package/@dynomapper/mcp-server)
• Working installation for at least one major MCP client (Claude Desktop, Cursor, etc.)
• Response to issues within a reasonable timeframe

Your metadata needs:

• Correct transport type (stdio, SSE, or HTTP)
• Category tags that match how developers search
• A short description under 160 characters for directory listings

Prioritization: Where to Start

If you’re short on time, hit these five first:

1. Official MCP Registry (registry.modelcontextprotocol.io) — credibility anchor
2. Smithery (smithery.ai) — CLI-integrated, highest developer reach
3. Glama (glama.ai/mcp) — largest index, auto-pulls from GitHub
4. MCP.so (mcp.so) — high volume, easy submission
5. Official GitHub Repo (github.com/modelcontextprotocol/servers) — backlink and trust signal

After those, work through the awesome lists. They’re low-effort PRs with solid long-term returns.

Keep Your Listings Fresh

Submitting once isn’t enough. Directory rankings favor active servers. Here’s what moves the needle:

• Keep your GitHub repo updated with meaningful commits
• Respond to issues and PRs promptly
• Update your description when you add new capabilities
• Claim your server on platforms like Glama that have owner verification
• Announce new versions to the communities around these directories

The MCP directory ecosystem is still consolidating. New directories launch regularly. Check back here for updates, and pay attention to which directories are gaining traction in developer communities on Reddit, Discord, and X.

The developers who treat distribution like a product feature — not an afterthought — are the ones whose servers actually get used.

Using Dyno Mapper’s sitemap and content audit tools with an AI agent? Install the Dyno Mapper MCP server and connect your AI client directly to your site’s structure.

Have a directory that’s missing from this list? Drop it in the comments.