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 48 worth knowing. First, where your server needs to be, how to tell when it is ready, and how long each kind of catalogue takes. You do not need to be a developer to check any of it. The full list follows, and each entry opens to its requirements and what to prepare.
Where Your MCP Server Needs to Be
Pick by where your customers already work. Most B2B products start with Claude, ChatGPT and Grok Bot. Microsoft and AWS reach large companies: Microsoft through the Copilot their staff already use, AWS through a store for teams building their own agents. Meta is still early access.
The AI assistant marketplaces
- Puts your product inside
- Claude on the web, desktop and mobile, including Cowork
- Who finds you there
- Claude users, who add connectors from inside Claude
- Company check
- Submitted from a paid Claude organisation
- Worth it when
- Almost always
- Puts your product inside
- ChatGPT, in the tools menu and at chatgpt.com/apps
- Who finds you there
- ChatGPT users
- Company check
- Organisation verification, individual or business
- Worth it when
- Almost always
- Puts your product inside
- Grok Bot, the Cursor code editor and the Grok assistant (coming soon), from one form
- Who finds you there
- Grok Bot users on SuperGrok and Cursor paid plans, and developers in Cursor
- Company check
- Identity and business checks by Anysphere, the company behind Cursor
- Worth it when
- Almost always; Cursor matters most if developers use you
- Puts your product inside
- Microsoft 365 Copilot, the assistant inside Word, Excel, Outlook and Teams
- Who finds you there
- People at companies on Microsoft 365, once their IT admins allow your agent
- Company check
- A Microsoft Partner Center account and a verified publisher domain
- Worth it when
- Your buyers are larger companies standardised on Microsoft
- Puts your product inside
- No assistant. AWS customers buy tools here to plug into agents they build themselves, for example on Amazon Bedrock AgentCore
- Who finds you there
- Engineering and procurement teams who buy through their AWS account
- Company check
- AWS seller registration through AWS Partner Central
- Worth it when
- You sell to enterprises that prefer to buy through AWS; skip it otherwise
- Puts your product inside
- Meta AI
- Who finds you there
- Meta AI users, once the programme opens; vendors are admitted in waves
- Company check
- Meta business verification and a 19-field application
- Worth it when
- Worth applying early; it is not a listing yet
Everywhere else
These need no review by a person, or only a light one. Start with the Official MCP Registry: several other catalogues copy their entries from it.
The Official MCP Registry
registry.modelcontextprotocol.io
How: Your developer publishes a server.json with a command-line tool, after proving you own the domain
Community directories
Smithery, mcp.so, MCP Market, MCPServers.org, LobeHub
How: A web form, often just a repository or a server URL
GitHub lists
awesome-mcp-servers, Awesome MCP List, mcpHQ
How: A pull request in the list's own format
Developer-tool catalogues
Cursor Marketplace, Docker MCP Catalog, Cline, Gemini CLI
How: A repository with the tool's own manifest file, or a pull request
When You Are Ready to Submit
You can submit before every feature exists. A marketplace reviews the server as it is today. Five tools that work pass; twenty tools with two broken do not. Reviewers check that the tools work for a stranger who signs up fresh, that the listing promises only what those tools do, and that the paperwork is in place.
The five checks below take fifteen minutes in Claude and need no developer. What you see there is what a reviewer sees.
1. Is the server hosted?
Look at what your developer gave you. A web address starting with https:// that you add under Settings, Connectors, Add custom connector means hosted. Setup steps that mention npx, pip, Docker or a config file mean installed.
- Passes: Hosted
Claude, ChatGPT, Grok Bot and Microsoft 365 take hosted servers only. Installed servers still fit the registry, community directories and GitHub lists.
2. How does a user sign in?
Remove the connector, add it again and watch. A login window for your product with an Allow button is OAuth. Being asked to paste a key or token is not.
- Passes: A login window opens
The reviewed marketplaces require OAuth for any tool that reads a user’s data.
3. Do the tool names make sense to a customer?
Ask Claude which tools it has from your product, then read the names in the "Claude wants to use…" prompts while it works.
- Passes: "Find open violations" passes; "Api read" or "Search api" does not
Reviewers and assistants both read the tool names to understand what your server does.
4. Does a customer see only their own data?
Sign in as an ordinary customer, not as staff, and ask for another customer by name.
- Passes: Nothing comes back for the other customer
An early connector is often built with a staff login that can search every client. A reviewer signs in as a customer and checks this first.
5. Are the answers right?
Ask the three or four questions your customers ask most, and compare each answer with your own dashboard. Then ask for something it cannot do.
- Passes: Numbers and dates match, and it says when it cannot do something instead of inventing an answer
A listing promises what the tools do. An answer that is wrong in review is a rejection.
What each stage lets you submit to
Stage 0: Start now, while the server is being built
Unlocks: Nothing is listed yet, but this is often the slowest part
- Company verification started for each marketplace you picked
- A paid Claude organisation to submit from
- Someone who can add a DNS record or a file to your website
- Privacy policy and terms pages live on your site
- A support email that someone reads
Stage 1: Ready for the open catalogues
Unlocks: The Official MCP Registry, community directories, GitHub lists and developer-tool catalogues
- The server is reachable at a stable address, or installable as a package
- Every tool you list works when you try it
- The description names only what those tools do
- A public GitHub repository, even if it only holds a README
Stage 2: Ready for the reviewed marketplaces
Unlocks: Claude, ChatGPT, Grok Bot, Microsoft 365, AWS and Meta
- All five self-checks pass
- Every tool is labelled read-only or destructive (ask your developer)
- A reviewer test account with real-looking data and a password that still works in two months
- Three or four test prompts; ChatGPT asks for five that should work and three that should not
- A short demo video, which ChatGPT asks for
- For Cursor and Grok Bot: a permissive licence such as MIT on any open-source part, and no charge for the plugin itself
Changing tools after approval is not always free. Cursor and Grok Bot review every new version again, while ChatGPT rescans your server daily and updates the listing. Submit to the reviewed marketplaces when what you have is the version you are happy to have reviewed.
Timeline
The open catalogues list you within days. The reviewed marketplaces took three to more than five weeks, and none publishes a review time. That wait is why the paperwork starts before the server is finished.
- Official MCP Registrysame day · stated
- MCP.Directory1 day · stated
- MCPServers.org, free queue14 days · stated
- ChatGPT Apps Directory22 days · observed
- Claude Connectors Directory33 days · observed
- Cursor Marketplace39+ days, still waiting · observed
- Grok Build marketplace39+ days, still waiting · observed
Dark bars: reviewed marketplaces. Light bars: open catalogues. Observed: one product submitted to four marketplaces on 1 October 2026 and checked on 9 November. Stated: the catalogue's own submission page.
When to start each
1. Company checks for the big marketplaces
Start: Today. Nothing here needs the server
Wait: Not published
2. The Official MCP Registry
Start: First, as soon as Stage 1 passes
Wait: Live at once. Glama, the GitHub MCP Registry and VS Code read from it
3. Community directories
Start: The same day as the registry
Wait: A day to six weeks free; several sell next-day review for USD 19 to 39
4. GitHub lists
Start: The same day as the registry, because the queue is long
Wait: Weeks. One list had 140 open pull requests and 20 merged in a month
5. Developer-tool catalogues
Start: Stage 1, if developers use your product
Wait: A day (Docker, Gemini CLI) to more than five weeks (Cursor, Grok Build)
6. AI assistant marketplaces
Start: Stage 2, all in the same week
Wait: Three to five weeks or more; none publishes a review time
Here Is How You Start
Today: start the company checks for the marketplaces you picked, and prepare the assets every submission asks for. None of it needs the server.
- A name and a one-line description of 100 characters or fewer
- A longer description written around jobs ("find open invoices over 30 days")
- A square logo, plus a version on a solid background
- Categories and a homepage or MCP landing page
- Privacy policy, terms and a support contact
- A documentation page: what each tool does and how to connect
- A reviewer test account with data, and the steps to sign in
- Test prompts and what should come back
- A short demo video
Send your developer these questions. Each is a yes or no, with the reason a marketplace asks.
- Is the server hosted at a public https:// address, using Streamable HTTP? The big marketplaces accept nothing else.
- Does sign-in use OAuth 2.0? Claude, ChatGPT and Microsoft 365 require it for tools that read a user’s data.
- Does each tool have a title and a read-only or destructive label (tool annotations)? Claude and Microsoft 365 require them.
- When a customer signs in, does every tool return only that customer’s data? A reviewer tests this first.
- Can we create a reviewer account with sample data that stays valid for months? Reviews can start weeks after you submit.
- Can you add a DNS TXT record or a file under /.well-known/ on our domain? The Official MCP Registry and ChatGPT use it to prove the server is yours.
- Is there a public repository, and what licence is it under? GitHub lists need one; Cursor and Grok Bot refuse copyleft licences such as GPL.
- What is planned next, and when? So the listing does not promise it yet, and you know whether to submit now or after the next release.
When Stage 1 passes: publish to the Official MCP Registry, then submit to the community directories and GitHub lists the same day.
When Stage 2 passes: submit to every reviewed marketplace in the same week, keep the reviewer account working, and answer review emails quickly. Cursor and Grok Bot follow up by email and have no status page. For one form worked through field by field, see how to submit to the Grok Bot marketplace.
Let Your AI Agent Do the Submitting
Ask Claude Code, Cursor or another agent to "list my MCP server using https://blastra.io/directories/mcp-directories/". The same list, with each catalogue's requirements, is at /directories/mcp-directories.json. It is free and needs no account.
Instructions for agents
- Collect the facts every catalogue asks for before submitting anywhere: the public repository URL, the remote server URL (Streamable HTTP) if it is hosted, the npm, PyPI or Docker package if it runs locally, a name, a one-line description of 100 characters or fewer, a longer description, categories, a square logo, a homepage, how a user authenticates, a privacy policy URL, and a test account for reviewers. Read the repository first and ask the user only for what is missing.
- Publish to the Official MCP Registry first: add a server.json and run mcp-publisher publish. Glama, PulseMCP and the GitHub MCP Registry read from it and take no separate submission. Check after a few days and claim the Glama listing; whether GitHub picks up every registry entry is not confirmed, so report it as unconfirmed rather than done.
- Then go through the catalogues in /directories/mcp-directories.json. The list is sorted by the host site's domain rating, which is not a priority order, so plan the order yourself: a requirement can name another catalogue to list on first (the punkpeye awesome lists need a Glama listing). Read each one's requirements before starting, and skip any they rule out: remote-only catalogues for a local server, repository-only lists for a closed-source one, and any whose requirements say submissions are paused or closed.
- For a GitHub list, read its CONTRIBUTING file and open one pull request per list, in the format and category it asks for.
- For an AI client directory (Claude, ChatGPT, Cursor, Microsoft 365 and similar), prepare everything it asks for and leave identity verification, legal agreements and the final submission to the user.
- Ask the user before creating an account, paying for a faster review, or getting past a captcha.
- Finish with three lists for the user: submitted (with links), waiting on review, and needs the user. Note each listing URL once it is live.
MCP Directories (48)
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.
Google's gallery of extensions for Gemini CLI, its command-line coding agent. An extension can bundle an MCP server. There is no submission form: the gallery indexes public GitHub repositories tagged gemini-cli-extension.
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 concise awesome list of MCP servers on GitHub, one line per server with its GitHub star count. It had about 900 stars on 2026-10-28.
The most-starred awesome list of MCP servers on GitHub, run by the team behind Glama and synced with Glama's web directory. It lists servers that have a public GitHub repository and run locally; it had about 97,000 stars on 2026-10-28.
A curated table of official remote MCP servers kept by an individual maintainer, separate from punkpeye's list of the same name. It had about 1,200 stars on 2026-10-28.
The remote-server companion to punkpeye's awesome-mcp-servers list, also run by the Glama team. It lists hosted MCP servers by endpoint URL and had about 2,100 stars on 2026-10-28.
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 directory of remote MCP servers run by ThinkChain Inc., which also hosts the connection: users add a listed server to Claude, Cursor, ChatGPT or VS Code through an MCP Bundles URL. Its public catalogue held over 1,000 servers in October 2026.
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.
A curated directory of agent skills, MCP servers and workflows. Entries are selected rather than crawled, and each MCP server page shows the result of the site's automated security audit. It listed 139 MCP servers and 193 skills in October 2026.
The MCP server section of AIBase, a Chinese AI news and tools site, available in Chinese, English and Japanese. It claimed over 121,000 listed services in October 2026.
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 free directory of plugins and MCP servers for AI coding agents such as Claude Code, Codex, Cursor and Grok, run by Hashgraph Online (HOL). It listed 877 plugins in October 2026.
A curated registry of MCP servers that gives each server a 0 to 100 quality score from maintenance, installs, stars, verification and documentation. Every server is reviewed by hand before listing. It listed 61 servers in October 2026.
A small curated directory of official and community MCP servers, browsed by category with setup instructions on each page. It listed 54 servers in October 2026.
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.
An editorially reviewed MCP directory that groups servers into use cases and stacks and shows install steps, client support and security notes for each server.
A community directory of MCP servers and MCP clients, with categories, featured and official sections, and setup guides.
A directory of MCP servers grouped by category, with learning guides and tools such as a config generator. It listed several hundred servers in October 2026.
An independent feed of MCP servers, plugins, skills and connectors for Claude Code and other agents. It is not affiliated with Anthropic and is separate from Anthropic's own Claude connector directory.
A directory of MCP servers and agent skills that writes install configs for Cursor, Claude and ChatGPT. It indexed over 14,000 servers in October 2026.
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.
A ranked list of about 400 MCP servers in 34 categories, re-ranked weekly by a quality score computed from GitHub metrics such as stars, contributors and recent commits. It had about 160 stars on 2026-10-28.
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 Bot, its always-on agent app. One submission form lists an MCP server in Grok Bot, in Cursor and, marked as coming soon, in the Grok assistant.
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 in-app marketplace of Kilo, an open-source AI coding agent, opened from the Kilo sidebar. It lists MCP servers alongside agents, skills and plugins, and is kept as a GitHub repository that takes pull requests.
A link-checked catalogue of MCP servers whose source is data/servers.json on GitHub. The README, a searchable website and a JSON API at mcphq.org/api/servers.json are generated from it. It had about 190 stars on 2026-10-28.
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.
The connectors Perplexity offers in its app and its Agent API, such as GitHub, Slack, Notion and Linear. There is no public submission form; Perplexity's API documentation says to email api@perplexity.ai to request a connector that is not listed.
Raycast's MCP Registry extension, a catalogue of MCP servers that Raycast users can install into Raycast, Claude or Cursor. It lists official and community servers kept in the extension's source, plus servers pulled from Smithery.
TensorBlock's awesome-mcp-servers list on GitHub, which also feeds a hosted MCP index with a website and a free public API. It indexed about 7,700 server links and had about 1,000 stars on 2026-10-28.
Stacklok's curated catalogue of MCP servers for ToolHive, its tool for running MCP servers in containers. Entries are server.json files in the stacklok/toolhive-catalog repository; on 2026-10-27 Stacklok cut it to 86 servers from established vendors and Stacklok itself.
ToolSDK's open registry of MCP servers, kept as JSON files on GitHub and published as an npm package and a browsable site. It listed about 5,200 servers and had about 200 stars on 2026-10-28.
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.

