An MCP server lets AI assistants such as Claude, ChatGPT and Cursor use your product directly. People find these servers in catalogues that work much like software directories: each has a listing with your name, a description and a way to connect, and each listing stays as you left it until you change it.
Blastra researched where MCP servers get listed and how each catalogue takes submissions, and put together the 23 worth knowing. Open any of them for its requirements, approval time and what to prepare.
Three Kinds of MCP Catalogue
Directories inside the AI clients (Claude, ChatGPT, Cursor, Docker, Microsoft 365, AWS) put your server one click away from the people using them. They review each submission and ask for things only you can provide, such as your own developer account, a reviewer test account and policy answers.
Community directories such as mcp.so, MCP Market and mcpservers.org take a web form or a repository link. Several offer a paid fast track with a badge.
Aggregators such as Glama, PulseMCP and the GitHub MCP Registry pick servers up from the Official MCP Registry, so publishing there first gets you into the others without separate submissions.
MCP Directories (23)
Sorted by domain rating. Click any catalogue for how to get listed there.
A directory of MCP servers and agent skills, sorted by category. Vendors submit a GitHub repository URL and choose a free or paid tier.
The MCP plugin marketplace of LobeHub, an open-source AI chat app. Listings can be installed into LobeHub and other compatible clients.
The website of the wong2 awesome-mcp-servers list. Vendors submit a server through a web form with name, category, description and link.
An AI tools directory with a section for MCP servers grouped by the service they connect to. Listings are bought as an annual subscription.
A community directory of MCP servers and clients. Vendors submit a repository URL and a name, with a paid option for a featured, verified listing.
A catalogue and hosting gateway for MCP servers. Vendors publish by pasting a server URL, through a command-line tool, or by uploading a bundle.
A directory of MCP servers and clients with a weekly newsletter. New submissions and edits are paused, and the site says it will import official registry entries when it reopens.
A large catalogue of MCP servers indexed from GitHub, plus a connectors section that imports remote servers from the official MCP registry. Each listing carries a quality score badge.
A community-run directory of Cursor rules and MCP servers, separate from Cursor's own marketplace. Members sign in and submit entries through a form.
Meta's connector programme for Meta AI, currently an early-access preview. Vendors apply through a form and are admitted in waves.
The public registry of MCP servers run by the Model Context Protocol project. Vendors publish a versioned server.json with the mcp-publisher command-line tool after proving they own the namespace.
A directory of MCP servers with publisher pages and install configurations for major clients. Vendors submit a GitHub repository and the site pulls the metadata and tool list from it.
The AI agents and tools category of AWS Marketplace, where vendors list MCP servers and agents that AWS customers can buy and deploy. Listings can be a hosted API endpoint or a container for Amazon Bedrock AgentCore.
OpenAI's directory of apps that run inside ChatGPT, built on MCP. Apps are reviewed before they appear, and ChatGPT users find them in the tools menu or at chatgpt.com/apps.
Anthropic's directory of remote MCP connectors that Claude users can add from inside Claude. Submissions go through a developer portal, pass an automated scan and are listed as Community by default.
The plugin section of Anthropic's directory, for plugin bundles used in Claude Code and Cowork. The portal reads a public GitHub repository and updates the listing when the repository changes.
The in-app catalogue of MCP servers for Cline, an AI coding agent for VS Code. Vendors request a listing by opening a GitHub issue from a template.
Cursor's official marketplace of plugins for its code editor, including MCP servers. Vendors submit a public Git repository and Cursor reviews every version by hand.
Docker's catalogue of MCP servers, used by the MCP Toolkit in Docker Desktop. Vendors add a server through a pull request to the docker/mcp-registry repository, which Docker reviews.
Figma's set of vetted partner MCP connectors shown in the Figma agent and Figma Make. Figma is collecting expressions of interest and vets partners against its security and privacy standards.
GitHub's catalogue of MCP servers, which supplies the one-click install buttons in VS Code. It has no submission form of its own.
xAI's plugin marketplace for Grok Build, kept as a GitHub repository. Vendors add a plugin with a pull request that pins a commit of their own plugin repository.
The store of agents inside Microsoft 365 Copilot. An MCP server reaches it by being wrapped in a declarative agent and submitted through Microsoft Partner Center.
Keep Your Story in Sync Everywhere
Your MCP listings are submitted from your own accounts. Blastra takes care of the software directories and review sites: we list you where it matters, keep every listing current as your product changes, and show you what AI reads about you.
Get StartedHow we curate this catalog
Editorially curated — we don't work with spam directories or freshly created sites. Before we add a directory, we check:
- Traffic starts at roughly 100k+ monthly visits for general directories (Similarweb).
- For niche directories, a lower traffic threshold, sometimes around 10k, because a focused, relevant listing carries real value.
No paid placement — a spot in this catalog can't be bought.
Run a directory and think it fits? Email ceo@blastra.io.

