Awesome Mcp Registries

---

Why this list? You finish building an MCP server and immediately hit the next question: "where do I list it so people — and AI clients — can actually find it?" The answer is scattered across blog posts and half-remembered tweets. This list gathers the destinations in one place, sorted by type, and tells you how each one wants submissions so you can go down the list. Every link is a real, working destination.

Contents

• Start Here — The Official Registry
• Auto-Indexing Directories (claim your listing)
• Submission-Based Directories & Registries
• Awesome Lists (open a pull request)
• Client Galleries & Marketplaces
• Before You Submit — a Checklist
• Related Awesome Lists
• Contributing

Start Here — The Official Registry

Do this first: most other directories are downstream of the official registry and mirror or link back to it.

• modelcontextprotocol/registry — The official, canonical MCP Registry. You publish with the mcp-publisher CLI (mcp-publisher login then mcp-publisher publish) using a server.json manifest that describes your server, packages and remotes.
• registry.modelcontextprotocol.io — The live registry API that serves the published entries (browse/consume programmatically).
• MCP Registry docs — Official documentation on the registry, server.json and the publishing flow.
• modelcontextprotocol/servers — The reference-servers repository; a PR here is the path for reference / notable community servers.

Auto-Indexing Directories (claim your listing)

These crawl public GitHub and hosted endpoints automatically — you mainly need to make your repo discoverable and then claim ownership of the listing.

• Glama — Large registry + inspector that auto-indexes open-source servers from GitHub, extracts every tool/schema/annotation, and assigns a quality score. Claim your server to manage its listing and badge.
• PulseMCP — Actively maintained directory with fast updates and strong support for remote HTTP servers. Submit at pulsemcp.com/submit.
• mcp.so — One of the largest, high-traffic MCP directories. Submit via the web form at mcp.so/submit.

Submission-Based Directories & Registries

These expect an explicit submission — a web form, a CLI publish, or a GitHub connect flow.

• Smithery — Popular registry used by many developers; publish via the smithery CLI or connect a GitHub repo (declare transport, e.g. http).
• Cursor Directory — MCP directory for the large Cursor editor community; submit via its web form.
• mcpservers.org — Lightweight community directory; quick web / GitHub submission.
• Fleur — App-store-style marketplace for MCP; submit your server for listing.
• mcp.run — Hosted registry/runtime for MCP "servlets"; publish to make servers installable.

Awesome Lists (open a pull request)

GitHub awesome lists are PR-based and give strong backlinks. Read each list's CONTRIBUTING first — several require a specific one-line format (and some server catalogs require a badge/emoji per entry).

• punkpeye/awesome-mcp-servers — The canonical, largest awesome list of MCP servers. Server entries require owner/repo link, a Glama score badge and a language emoji; open a PR from the correct fork of this network.
• wong2/awesome-mcp-servers — Another widely referenced awesome list (a separate GitHub network from the one above).
• appcypher/awesome-mcp-servers — A large early list (archived / read-only — historical reference).
• AIAnytime/Awesome-MCP-Server — Actively maintained catalog with category sections (e.g. commerce, travel & logistics).
• TensorBlock/awesome-mcp-servers — Very large, categorized awesome list that accepts server PRs.
• MobinX/awesome-mcp-list — A concise, curated list of MCP servers.

Client Galleries & Marketplaces

Some MCP clients ship their own in-app gallery or extension store — getting listed there puts your server in front of that client's users.

• VS Code MCP — Visual Studio Code's MCP support and curated server gallery.
• Cursor Directory — Doubles as the Cursor editor's in-context MCP gallery.

Before You Submit — a Checklist

Have these ready so any form or PR goes smoothly:

• A public GitHub repo with a clear README (bilingual is a plus).
• A server.json manifest describing your server, packages and/or remotes.
• A live endpoint (for remote servers, a Streamable HTTP URL that responds) or an installable package.
• A one-line description, a category, and a few tags.
• A square logo (≥ 512×512 PNG) for directories that show one.
• Verify your server first with a conformance smoke test so you don't submit a broken endpoint — e.g. mcp-conformance (npx mcp-conformance <url>) or the official MCP Inspector.
• Optional: an llms.txt for AI crawlers.

Related Awesome Lists

• awesome-mcp-servers — The canonical list of MCP servers themselves.
• awesome-mcp-testing — Tools to test, evaluate and validate MCP servers before you ship them.
• awesome-mcp-devtools — Dev tools, SDKs and libraries for building MCP servers.
• Model Context Protocol — The official protocol site and documentation.

Contributing

Contributions welcome — see CONTRIBUTING.md. In short: the destination must be real and the link must work (HTTP 200), it must genuinely be a place to publish/list/submit an MCP server, one item per pull request in the right section, with a one-line factual note on how to submit. Add it to both README.md and README.vi.md.

License

CC0 — released under CC0 1.0 Universal. To the extent possible under law, the contributors have waived all copyright and related rights to this list. Each listed destination keeps its own terms — always check the source before use.