List your MCP server in three layers. Publish once to the official MCP Registry, submit to the six to eight directories developers browse (Glama, PulseMCP, mcp.so, MCP Market, the Docker MCP Catalog and awesome-mcp-servers), then apply to the client install pages where people click Install: the Claude Connectors Directory, the ChatGPT Plugin Directory and the Cursor Marketplace.
Getting listed is the easy part. The official registry already holds 65,948 servers by our count of its public API, and when we audited 10 well-known SaaS vendors, 9 of their 61 official listings showed an old endpoint or an outdated description. So the real job is getting picked, and that comes down to how consistent your listing is everywhere it appears.
This blog gives you the full list of 42 platforms we checked, what each one asks for, which kind of MCP server it suits, and the order we would submit in. You can export the whole list as an Excel tracker right below the directory.
TL;DR
- The official MCP Registry is the upstream feed. GitHub's registry, VS Code, and several aggregators read from it, but Claude, ChatGPT, Cursor, and most directories still need their own submission.
- Remote SaaS servers and local devtool servers need different listing plans. SaaS lives or dies on OAuth and client directories; devtools on npm, GitHub lists and install friction.
- Copies drift. In our audit of 10 vendors across 7 surfaces, 9 of 61 official listings were stale, and 9 more slots were empty or held only a third-party server.
- Every surface has its own field limits (30 characters on OpenAI, 100 in the registry, 200 on Anthropic's one-liner), so write one canonical description in three lengths.
- Listing checklists rot fast. Six of the 24 links on a typical MCP submission checklist we were handed are now dead, archived or closed to self-serve submissions.
The complete MCP listing directory for 2027
We checked every platform below, along with its submission path, requirements, and size. Priority assumes you sell a B2B SaaS product or a developer tool. "Must" means list in week one, "High" means list in your first month, "Medium" means list if the platform fits your server type, and "Low" means list only once everything above is done.
Filter by type or priority, or search for what your server needs (OAuth, Docker, npm, enterprise). Every tile links straight to the platform's submission page.
Registries6
Publish here first. These feed the directories and clients downstream.
GitHub MCP Registry
MustDefault discovery surface for Copilot and VS Code users
- Best for
- SaaS and devtools targeting GitHub Copilot and VS Code users
- How to submit
- Publish to the official registry, then request inclusion (partnerships@github.com)
- Cost
- Free
- Review
- Curated, criteria not published
- Size
- 896 servers listed
What you need to submit
Same as the official registry; curated list of partner and community servers
Official MCP Registry
MustOne publish reaches the aggregators and clients that sync from it
- Best for
- Every public MCP server, local or remote
- How to submit
- mcp-publisher CLI with a server.json (GitHub Actions OIDC supported)
- Cost
- Free
- Review
- Automated validation at publish
- Size
- 65,948 servers (latest versions); 44,797 expose a remote endpoint
Watch out: Still labeled preview, and publishing passes an automated check with no human review.
What you need to submit
Public package on npm, PyPI, NuGet, OCI, MCPB or Cargo with ownership proof (npm mcpName, PyPI/NuGet/Cargo mcp-name line, OCI label), or a public remote URL. Namespace verified through GitHub, DNS or HTTP.
npm (keywords mcp, mcp-server)
MustThe install layer every directory links to
- Best for
- Local TypeScript and JavaScript servers
- How to submit
- npm publish with keywords; add mcpName for the official registry
- Cost
- Free
- Review
- None
- Size
- 91,418 packages tagged mcp; 11,703 tagged mcp-server
What you need to submit
npm account; mcpName in package.json
Docker MCP Registry and Catalog
HighSandboxed one-click installs and signed images that enterprise teams trust
- Best for
- Docker-packaged local servers; remote servers wanting Docker Desktop reach
- How to submit
- PR adding servers/<name>/server.yaml to docker/mcp-registry
- Cost
- Free
- Review
- Docker team reviews every PR; live within 24 hours of approval
- Size
- 300+ verified servers; popular entries show 1M+ pulls
What you need to submit
Local: public repo with a Dockerfile, permissive license (MIT or Apache 2), passing CI, test credentials. Remote servers accepted too.
API Tracker MCP servers
MediumPicks you up from the official registry anyway; claim to correct the entry
- Best for
- API-first SaaS that also lists APIs
- How to submit
- Web form; also auto-ingests the official registry
- Size
- 167,897 source listings; 30,743 setup-eligible endpoints
ToolHive Registry (Stacklok)
MediumCurated enterprise registry run by the team leading the registry working group
- Best for
- Security-conscious enterprise teams running ToolHive
- How to submit
- Web form or PR to stacklok/toolhive-catalog with a server.json
- Cost
- Free
- Review
- Stacklok team review
- Size
- Small curated catalog
What you need to submit
Container-based or remote server; reviewed and verified by Stacklok
Directories18
Where developers browse and compare servers.
punkpeye/awesome-mcp-servers
MustThe most-starred MCP list on GitHub
- Best for
- Local OSS servers
- How to submit
- PR to README
- Cost
- Free
- Review
- Maintainer review
- Size
- 97,759 GitHub stars; 20,099 forks
What you need to submit
Public GitHub repo you install and run yourself; remote-only servers go to the remote list
Glama
HighBiggest index, and its health checks show up on your page
- Best for
- Local OSS servers and remote connectors
- How to submit
- Add Server button; claim your server; list remote servers as connectors
- Cost
- Free
- Review
- Automated indexing plus health checks
- Size
- 122,052 servers; 11,838 claimed
Watch out: Glama shows uptime on your page. Supabase's entry read "Unhealthy, 0.0% uptime" because the check could not log in, so give it a public health path.
What you need to submit
Public repo or remote endpoint; Glama runs health checks
MCP Market (mcpmarket.com)
HighCited in Google's AI Overview for 'mcp marketplace'
- Best for
- Local OSS and remote servers, plus agent skills
- How to submit
- Web form: GitHub repo or remote MCP URL
- Cost
- Free, or $29 one-time
- Review
- Free queue 4 to 6 weeks; paid listing within 24 hours
- Size
- 35K+ servers; 200K+ agent skills
What you need to submit
Repository URL
Postman MCP Catalog
HighReaches developers while they test your API
- Best for
- API-first SaaS already on Postman
- How to submit
- Become a verified publisher; publish a public MCP collection
- Cost
- Free
- Review
- Automatic for verified publishers
What you need to submit
Public team profile and workspace; verified publishers appear automatically
PulseMCP
HighWell-read directory and weekly newsletter in the MCP builder community
- Best for
- All servers; strong with builders who read its newsletter
- How to submit
- Web submission form
- Cost
- Free
Watch out: Run by Tadas Antanavicius, one of four official registry maintainers.
What you need to submit
Not verifiable (site blocks automated access)
mcp.so
HighHigh-traffic directory that Google cites for 'mcp marketplace'
- Best for
- Local OSS and remote servers
- How to submit
- Web form: repository URL (or hosted endpoint for remote)
- Cost
- Free, or $39 one-time Premium (verified badge, dofollow link)
- Review
- Free review (time not stated) or instant with Premium
- Size
- 20,733 servers
What you need to submit
Repository URL; hosted endpoint for remote servers
punkpeye/awesome-remote-mcp-servers
HighRemote-only counterpart of the biggest list; strong fit for B2B SaaS
- Best for
- Remote SaaS servers with OAuth
- How to submit
- PR to README
- Cost
- Free
- Review
- CI handshake check plus maintainer merge
- Size
- 3,263 GitHub stars; 2,094 entries
Watch out: CI calls your URL with an MCP initialize request on every PR, and you need a Glama connector listing first.
What you need to submit
Public URL that answers MCP initialize (CI checks it); usable by anyone; Glama connector listing; auth marker; description up to 120 chars
MCP Marketplace (mcp-marketplace.io)
MediumRanks top 3 for 'mcp marketplace' and is the only one with built-in monetization
- Best for
- Creators who want to sell or monetize a server
- How to submit
- Listing form; set free or paid pricing
- Cost
- Free to list; paid pricing via Stripe (commission not stated)
- Review
- Most approved within minutes after scan
- Size
- 53,600+ security-scanned servers (homepage)
What you need to submit
Must follow the MCP protocol; automated security scan (protocol, code safety, dependencies)
Smithery
MediumChanged
Still a known name, but Smithery is now part of Arcade and its proxy and managed identity shut down on 31 Oct 2026
- Best for
- Remote servers from verified vendors
- How to submit
- Self-serve publish closed (/new returns 404); now a curated set of verified servers
- Review
- Curated by Arcade
Watch out: If you are already listed, check that your page still points at your current endpoint.
What you need to submit
Remote server over Streamable HTTP; OAuth if needed; server card at /.well-known/mcp/server-card.json
mcpservers.org
MediumOnly path into the wong2 awesome list
- Best for
- Local OSS servers
- How to submit
- Web form: name, category, description, link, email, optional registry name
- Cost
- Free, or $39 Premium (badge, DR 72 dofollow link)
- Review
- Free within 2 weeks; Premium within 24 hours
What you need to submit
Form fields only
AI Agents List
LowGeneral AI directory with a small MCP section
- Best for
- AI tool vendors wanting a backlink
- How to submit
- Web form
- Cost
- $29 or $49
- Review
- 24 to 48 hours
- Size
- 593 MCP servers
What you need to submit
Website eligibility check
Claude Market (claudemarket.ai)
LowPaid and independent (not Anthropic); Anthropic's directory matters far more
- Best for
- Claude Code users browsing skills and servers
- How to submit
- Web form with autofill from repo or MCP URL
- Cost
- $29 one-time
- Review
- Live within 48 hours
- Size
- 13,870+ servers
LobeHub MCP Marketplace
LowLarge app, but you cannot control inclusion
- Best for
- LobeHub app users
- How to submit
- No documented submission path
- Review
- Ranked on activity, stability and feedback
Stork.AI
LowQuick and free, small audience
- Best for
- Remote endpoints and npm servers
- How to submit
- Web form: npm name, GitHub URL or remote endpoint
- Cost
- Free
- Review
- Automated
What you need to submit
Endpoint verified with a real MCP handshake
appcypher/awesome-mcp-servers
LowLow activity
Slow-moving list
- Best for
- Local OSS servers
- How to submit
- PR, one server per PR
- Cost
- Free
- Review
- Maintainer merge; no push since May 2026
- Size
- 5,839 GitHub stars
What you need to submit
Short, useful description
mcp.directory
LowSmaller catalog
- Best for
- Local OSS servers and agent skills
- How to submit
- Submit Server form
- Size
- 2,303 servers
mcphub.io
LowUnreachable
Site did not load on 17 Nov 2026
wong2/awesome-mcp-servers
LowCovered by the mcpservers.org submission
- Best for
- Local OSS servers
- How to submit
- No PRs; submit through mcpservers.org
- Cost
- See mcpservers.org
- Review
- Via mcpservers.org
- Size
- 4,410 GitHub stars
What you need to submit
See mcpservers.org
Client install pages14
Where users click Install inside the product.
Claude Connectors Directory
MustIn-product install for Claude users
- Best for
- Remote SaaS and enterprise servers for Claude users
- How to submit
- Developer portal: Submit new, MCP connector (10 steps)
- Cost
- Free (needs a paid Claude plan)
- Review
- Automated policy scan, then listed as Community; some get human review and a Verified label
Watch out: No longer accepts local servers packaged as MCP Bundles. A local server has to ship inside a plugin.
What you need to submit
Remote HTTPS server; OAuth 2.0 for authenticated services; every tool needs a title plus readOnlyHint or destructiveHint; docs URL, privacy policy, support contact, icon, reviewer test account. Local servers only inside a plugin.
ChatGPT Plugin Directory
MustIn-product distribution to ChatGPT and Codex users
- Best for
- Remote SaaS with OAuth targeting ChatGPT and Codex users
- How to submit
- Upload plugin ZIP, verify domain, connect and scan the MCP server, submit for review
- Review
- Automated checks, then human review
Watch out: displayName and shortDescription are capped at 30 characters each.
What you need to submit
Stable public HTTPS endpoint; domain challenge at /.well-known/openai-apps-challenge; org verification; website, support, privacy and terms URLs; 5 positive and 3 negative test cases; video walkthrough
VS Code MCP page
MustRedirect
Covered by the official registry plus GitHub
- Best for
- VS Code and Copilot users
- How to submit
- No separate submission; redirects to github.com/mcp
- Cost
- Free
- Size
- See GitHub MCP Registry
What you need to submit
See GitHub MCP Registry
AWS Marketplace: AI Agents and Tools
HighBuyers can pay through their AWS bill
- Best for
- Enterprise SaaS that wants AWS procurement and AgentCore reach
- How to submit
- Partner Central listing wizard, product type MCP Server
- Cost
- AWS Marketplace fees apply
- Review
- AWS launch review
What you need to submit
AWS Marketplace seller; MCP endpoint; API key or OAuth 2.0; billing integration
Cursor Marketplace
HighOfficial in-product marketplace of a major AI IDE
- Best for
- Established SaaS and devtools targeting Cursor users
- How to submit
- Publish form; plugins distributed as Git repositories
- Review
- Every plugin manually reviewed
What you need to submit
Cursor plugin package (MCP server, skills, rules) in a Git repo
Gemini CLI extensions gallery
HighZero-effort listing through a GitHub topic
- Best for
- Local or remote servers for terminal agent users
- How to submit
- Auto-crawl: public repo with the gemini-cli-extension topic and gemini-extension.json
- Cost
- Free
- Review
- Automated validation, crawled daily
- Size
- 2,194 extensions
Watch out: The lowest-effort listing in this directory.
What you need to submit
Public GitHub repo; manifest at repo root
Microsoft MCP certification
HighGatekeeper to Microsoft's enterprise agent surfaces
- Best for
- Enterprise B2B SaaS selling into Microsoft 365 shops
- How to submit
- Partner Center offer plus certification intake form
- Review
- Functional, safety and responsible-AI review; limited preview intake
What you need to submit
Verified publisher; own the endpoint; manifest and tool file; Azure Key Vault auth config; OAuth 2.0 preferred
cursor.directory
HighCursor's docs send users here for community MCP servers
- Best for
- Community and OSS servers for Cursor users
- How to submit
- Web form: auto-detect from a GitHub repo or create manually
What you need to submit
Open Plugins format
Cline MCP Marketplace
MediumIn-product install for Cline users
- Best for
- Local OSS servers for Cline users
- How to submit
- GitHub issue with the submission template
- Cost
- Free
- Review
- Within a couple of days
- Size
- 199 servers
What you need to submit
GitHub repo; 400x400 PNG logo; Cline must install it from the README or llms-install.md
Kiro Registry
MediumShort official-only list means high visibility if accepted
- Best for
- Vendors targeting Kiro IDE and CLI users
- How to submit
- Web form
- Cost
- Free
- Review
- Curated
- Size
- 39 servers, all official
Watch out: An official-only list of 39 servers, so an accepted entry stands out.
What you need to submit
Public GitHub repo; Kiro publisher terms
Raycast MCP Registry
MediumCheap PR with a real install base
- Best for
- Remote servers for macOS power users
- How to submit
- PR adding an entry to entries.ts
- Cost
- Free
- Review
- Raycast PR review
- Size
- 45,106 installs of the registry extension
What you need to submit
Entry with config; remote servers can set remoteUrl
Azure MCP Center
LowStale
Repo idle since Sep 2025; use Microsoft's certification path
- Best for
- Azure ecosystem vendors
- How to submit
- Comment on GitHub issue #4
- Cost
- Free
- Review
- Requests unanswered
- Size
- 37 GitHub stars
What you need to submit
Remote servers should support streamable HTTP with OAuth 2.1
Zed MCP extensions
LowDeprecation announced
Publishing to the official registry covers Zed
- Best for
- Zed users, local servers
- How to submit
- Zed extension published via zed-industries/extensions
- Cost
- Free
What you need to submit
Binary or npm-published server
goose extensions directory
LowMoved
Small list, undocumented process
- Best for
- goose agent users, local servers
- How to submit
- PR to documentation/static/servers.json (undocumented)
- Cost
- Free
- Size
- 57 entries
No longer accepting listings
Still on older submission checklists, so skip these and save the time.
- MCP Harbor (unreachable): Connection resets; no documentation found
- MCP Find (dead): Deployment not found
- mcp-get (archived): No longer maintained
- Continue Hub (dead): Domain no longer resolves; Continue was acquired by Cursor
Get the full MCP listing tracker
All 42 platforms in one Excel file, with submit links, requirements, size, review time, cost and a status column for your team, plus a canonical listing kit sheet for your descriptions.
- Every platform in this directory, sorted by priority
- Track who submitted where, and when
- Character limits for each surface in one sheet
What is driving searches for "mcp marketplace"?
Two things explain the shift, and both change where you should spend effort:
- Clients built their own stores. Cursor, Claude, ChatGPT, VS Code and Docker Desktop now show install pages inside the product, so a developer never has to leave the editor to find a server.
- Agents search for tools on their own. At the MCP Dev Summit in April 2026, MCP co-creator David Soria Parra said MCP tools took 22% of a 200k-token context window in Claude Code before tool search, and close to zero after. Tool search picks tools by matching their names and descriptions, so your description now works like a ranking signal.
How does a listing reach a developer or an AI agent?
Your listing travels down a chain, and each link adds its own copy of your data. You publish a server.json to the official registry. Sub-registries such as GitHub, PulseMCP and the client stores pull from it, add their own data, and show it to people or agents.

The official MCP Registry homepage. Every card is pulled from a publisher's server.json, and several were updated the day we checked.

The registry docs say aggregators pull new metadata on a regular but infrequent basis, for example, once an hour, and that the metadata is "deliberately unopinionated".
Here is what that means in practice:
- The registry stores pointers to your code. It maps a name like com.yourcompany/server to an npm package or a remote URL, plus install instructions.
- The namespace is your trust signal. Reverse-DNS names are tied to a verified GitHub account or domain, so only you can publish under com.yourcompany.
- Curation happens downstream. The registry only checks your namespace and format. Its moderation policy says it won't remove low-quality, buggy or duplicate servers, and tells consumers to "assume minimal-to-no moderation". So every directory judges you on its own terms.
Tadas Antanavicius of PulseMCP put the problem plainly in the same registry talk: "discovery and MCP server selection is a very hard problem." His co-maintainer Toby Padilla summed up the design goal as "publish once, show up in many places". That works for surfaces that sync from the registry. Our audit below shows what happens on the ones that keep their own copy.

The GitHub MCP Registry listed 896 servers on 17 November 2026, a small curated slice of the 65,948 in the official registry.
Which listings fit a SaaS server, a devtool server, or an enterprise server?
The right list depends on how your server runs. A hosted SaaS server, a local developer tool, and an enterprise product are judged on different things, so treat them as three separate plans.

Priority order for remote SaaS, local OSS and enterprise servers, based on each platform's published requirements.
Remote SaaS servers win on OAuth and client directories
A SaaS server is a hosted URL that acts on a customer's account. The client install pages are built for exactly this, and they are strict:
- Auth: Claude asks for OAuth 2.0 on any tool that touches user data. OpenAI's portal does not support API-key auth.
- Tool design: Claude's reviewers read every tool's name, description and readOnlyHint or destructiveHint. A vague tool like do_action gets flagged.
- Reviewer access: both Anthropic and OpenAI need a populated test account that works without MFA codes or magic links.
Devtool servers win on install friction and GitHub signals
A devtool server usually runs on the developer's machine through npx, uvx or Docker. Developers judge it in about ten seconds, by the README, the stars and whether the install command works first time. So the listing work looks different:
- Package first: publish to npm or PyPI with the ownership tag, then the registry.
- GitHub lists carry weight: awesome-mcp-servers alone has 97,759 stars, and its entries get copied into dozens of smaller directories.
- Install files: an llms-install.md lets Cline (and coding agents generally) install your server without a human.
Suppose we have a company that ships both a hosted API and a local CLI. It needs two server.json entries, two descriptions and two sets of listings, because the hosted one goes to Claude and ChatGPT while the local one goes to npm, Docker and the awesome list.
Enterprise servers win on governance
Enterprise buyers rarely browse public directories. They install from a private catalog their platform team approves. Amit Arora, a principal solutions architect at AWS, described the need in an AWS Show and Tell as a central catalog "for discovering governed assets". That is why Microsoft certification, AWS Marketplace and signed images from Docker or ToolHive belong in an enterprise plan.
What did we find when we audited 10 vendors' MCP listings?
We checked whether 10 well-known SaaS vendors with official MCP servers are listed on 7 major surfaces, and whether each listing matches the vendor's own docs. The vendors were Stripe, Sentry, Linear, Notion, Supabase, Atlassian, Cloudflare, Neon, PayPal, and Figma.

Method: We queried the official registry, GitHub MCP Registry, and Docker catalog through their APIs and read Smithery, Glama, Cursor and VS Code pages.
What the numbers say:
- 61 of 70 slots carried the vendor's official server. 7 were empty and 2 held only a third-party server.
- 9 of those 61 showed an old endpoint or a description that no longer matches the product.
- 6 of the 10 vendors had at least one stale listing. Only Stripe, Linear, Supabase and Figma had none.
A few examples show how drift happens:
- Cloudflare: its registry entry says only "Cloudflare MCP servers", was last published in September 2025, and lists 15 per-product endpoints but not the consolidated server Cloudflare's docs now recommend. Docker still carries 14 separate entries on the older SSE transport.
- Atlassian: the registry is on v2 ("Jira, Confluence, Loom"), while Docker's entry still points at /v1/mcp and says "Jira, Confluence, and Compass".
- Neon: the registry's v2.0.0 describes "Lakebase Postgres", while GitHub's entry still says "Neon Management API" and points only at /sse.
The lesson for everyone else: if Cloudflare and Atlassian drift, a 20-person startup will too. Each surface keeps its own copy, and nothing re-syncs it for you once you change an endpoint or rename a product.
Why should you write one canonical listing in three lengths?
Every surface caps your text differently, so a single description cannot fit all of them. When teams rewrite copy per site, the versions drift apart, and an AI assistant comparing tools reads conflicting claims about you.
| Surface | Field | Limit |
|---|---|---|
| ChatGPT Plugin Directory | displayName, shortDescription | 30 characters each |
| awesome-remote-mcp-servers | description | 120 characters |
| Official MCP Registry | description in server.json | 100 characters |
| Claude Connectors Directory | server name / one-liner / description | 100 / 200 / 2,000 characters |
| ChatGPT Plugin Directory | longDescription | 4,000 characters |
So write the copy once, in three lengths, and paste from that source every time:
- Short (30 characters): what it does in a verb and an object. "Invoices and payments in chat."
- One-liner (100 to 120 characters): who it is for and the top two jobs. This also fits the registry's 100-character description if you keep it tight.
- Long (up to 2,000 characters): scope, data touched, auth model, and what the server never does.
Description quality also decides whether an agent picks you. In a study of 10,831 MCP servers, servers with standard-compliant descriptions were chosen 72% of the time against functionally equivalent rivals, compared with a 20% baseline. Most servers are not there yet: 97.1% of 856 tool descriptions in another study had at least one quality problem, and 56% did not state their purpose clearly.
The same rule applies to tool descriptions, since tool search reads them. Keep tool names, titles and annotations identical across server.json, your docs and every directory that shows a tool list. This is the same consistency problem we cover in our guide to getting into the lists AI engines cite: AI answers repeat whatever version of you they find most often.
Which MCP directories are worth paying for?
Pay only when you have a launch date. Five directories now sell a fast lane: mcp.so and mcpservers.org charge $39, MCP Market and Claude Market charge $29, and AI Agents List charges $29 to $49. In return you skip free queues that run from 2 weeks (mcpservers.org) to 4 to 6 weeks (MCP Market) and usually get a badge and a dofollow link.
Skip the paid tiers on independent sites that only resell visibility, and put that budget into the free surfaces with real install traffic. A measurement study of six MCP markets found only 49.1% of 17,630 entries were valid, and on MCP Market the share was 26.4%. A badge on a crowded directory buys less than it used to, and the same study found a third to two-fifths of projects already cross-listed in several markets.
Also check that a platform still exists before you budget time for it. Of the 24 links on the submission checklist we started from, six no longer take new listings:
- Smithery: self-serve publishing closed after the move to Arcade.
- Continue Hub: the domain no longer resolves, and Continue says it was acquired by Cursor.
- mcp-get: archived and no longer maintained.
- MCP Find and MCP Harbor: one returns a deployment-not-found error, the other resets the connection.
- Azure MCP Center: submissions are made as comments on a GitHub issue that has gone unanswered, and its showcase site does not load.
What security signals do listing reviewers check?
Reviewers check security because the public record is poor. Trend Micro found 1,467 exposed MCP servers in its latest scan, up from 492 in July 2025, many running without basic controls. And because the official registry delegates scanning, each directory now runs its own checks.
What to have ready before you submit:
- Auth that matches the data: OAuth 2.0 for user data, no auth only for public data.
- Honest tool annotations: mark every write action with destructiveHint; reviewers reject tools that hide side effects.
- A current transport: Streamable HTTP for remote servers. Several stale listings in our audit still pointed at legacy SSE endpoints.
- Signed or reproducible builds if you target Docker or enterprise catalogs.
- A privacy policy that covers collection, storage, sharing, retention and contact. Anthropic rejects local connectors without one.
How should you roll out MCP listings over 30 days?
Prepare one canonical kit, publish upstream, fan out, then audit every copy each month. The plan below is the order we use for DevTools and B2B SaaS clients.

Week 1 builds the kit. Week 4 starts a monthly sync check, the step our audit suggests many vendors miss.
Two habits keep the plan from decaying after launch:
- Republish from CI. Wire mcp-publisher into your release workflow so the registry version always matches the shipped version.
- Diff monthly. Compare each listing's endpoint, version and description against your canonical kit, and fix drift before an AI answer repeats it.
How Infrasity runs MCP distribution for DevTools
Listing an MCP server is a distribution project, and it pays off only when every listing tells the same story. That is the work we do at Infrasity: we prepare the canonical kit, write the tool descriptions, submit to the registries, directories and client stores that fit your server, and keep every copy in sync so AI assistants repeat accurate information about you.
For MemClaw, an open-source agent memory tool, we ran a listings pipeline across awesome lists, MCP directories (Glama, MCP.so and Smithery) and OSS discovery sites, alongside demo repos and Reddit engagement. In six weeks, the main repo went up 1,512% in stars, package downloads passed 31,000, and 7 placements went live with 9 more in review, with $0 in paid spend.
If you are launching or relaunching an MCP server, our AI agents GTM services cover the listings, docs, and launch content; our GitHub marketing team handles awesome-list and repo work, and our AEO and GEO team tracks whether ChatGPT, Claude and Perplexity name you.
Frequently Asked Questions
What is an MCP marketplace?
An MCP marketplace is a place where people or AI clients discover and install MCP servers. It can be a registry like the official MCP Registry, a directory like Glama or mcp.so, or an install page inside a client like the Claude Connectors Directory or the Cursor Marketplace.
Is publishing to the official MCP Registry enough?
No. The registry feeds GitHub's registry, VS Code and some aggregators, but Claude, ChatGPT, Cursor, Docker and most directories need their own submission. Treat the registry as the first step that makes every later listing easier to verify.
How long does it take to get an MCP server listed?
The official registry is instant once your server.json validates. Docker lists approved servers within 24 hours, free directory queues run from 2 to 6 weeks, and client stores like Claude, ChatGPT and Cursor review by hand on their own timelines.
Do I need OAuth to list a remote MCP server?
You need OAuth 2.0 if your tools act on a user's account and you want to be in the Claude Connectors Directory. Servers that only expose public data can run without auth, and OpenAI's portal supports no auth, OAuth or a mix of both, but not API keys.
Should a local devtool MCP server be listed in the Claude directory?
Not on its own. Anthropic's directory no longer accepts local servers packaged as MCP Bundles, so a local server has to ship inside a plugin. Most devtools get more from npm, the official registry, awesome-mcp-servers, Docker and Cline.
How do I keep MCP listings consistent across directories?
Keep one canonical listing kit with your description in three lengths, your tool list and your endpoint, republish to the registry from CI on every release, and check each directory against the kit once a month.









