Skip to main content
Back to Blog
industry-insightsFeatured

You Built a Hosted MCP Server. Where Can You Actually List It?

Sean Matthews
8 min read

Standing up a hosted MCP server doesn't list it anywhere: nothing crawls for servers, so every place you might appear is a submission. This post covers the chat clients (including Meta's Muse), IDE clients, registries and enterprise marketplaces, and how to get listed in each.

You Built a Hosted MCP Server. Where Can You Actually List It?
Left Hook

TL;DR

  • Start with one publish. The official MCP Registry is free and has no review, and aggregators and marketplaces are designed to pull from it. Glama, mcp.directory and PulseMCP import from it, and it's the first step toward GitHub's registry and VS Code's gallery.
  • Then the larger submissions: ChatGPT, Claude and Meta's Muse, plus Microsoft's and Google's enterprise paths. Each has its own process.
  • Most clients just take your URL. For those, give users a config snippet or a one-click link.

Does anything find your server automatically?

No. The 2026-07-28 spec added a server/discover RPC that servers must implement, but clients only call it once they already have your URL. It isn't a directory.

Server cards are the closest thing. SEP-2127 merged as a Final, optional extension on Oct 6, 2026. A card can live at <your-mcp-url>/server-card, and a domain can advertise cards at /.well-known/ai-catalog.json. That lets a client or crawler describe your server if it looks. We couldn't find a client that documents using cards to find servers yet.


Step 1: Publish to the official MCP Registry

Free, no review.

  1. Write a server.json with a com.<yourdomain>/<server> name and a remotes entry for your Streamable HTTP URL. No package is needed for a remote server.
  2. Authenticate with mcp-publisher login dns or login http, so the name reflects a domain you control. A GitHub login gives you io.github.<user>/* instead. Authentication guide.
  3. Run mcp-publisher publish, then confirm with a search on registry.modelcontextprotocol.io/v0.1/servers.

The registry verifies your namespace, not that the URL works, and it's still in preview. Clients aren't meant to read it directly; what matters is who pulls from it.


Registries and directories

Two of these have dependencies: Glama before awesome-remote (the PR needs a Glama connector badge), and the official registry before GitHub. Nothing else has to wait.

ChannelHow to listCost
GlamaImports from the official registry. Claim it by verifying your domain (DNS TXT or .well-known/glama.json)Free
GitHub MCP RegistryPublish to the official registry, then post an onboarding request in GitHub's discussion. Manual curation; needs a public repo and licenseFree
awesome-remote-mcp-serversOne PR. Needs a public endpoint that answers initialize, open sign-up and a Glama connector badge. The main Awesome MCP Servers list takes only reposFree
SmitheryEnter your public HTTPS URL at smithery.ai/new, then finish its verification checklistFree
Docker MCP CatalogRemote servers accepted. Run the remote wizard and open a PR; live about 24 hours after approvalFree
PulseMCP, mcp.directoryBoth import from the official registry. PulseMCP's submit page said submissions were paused as of Sep 29Free
mcp.so$39 publishing fee$39
MCP MarketFree queue (about 4-6 weeks) or a listing within 24 hours$0 or $29

These host or run servers and don't list yours: Composio, Apify and Cloudflare. Zapier MCP and Pipedream MCP expose their catalogs to AI clients; if you already have a Zapier integration, you're reachable there. Pipedream Workflows shuts down Mar 31, 2027; Connect and its MCP servers are unaffected.


ChatGPT, Claude, Muse, Microsoft and Google

Each has its own submission. Audience tiers: XL is hundreds of millions of users, L is millions or a dominant niche.

ChannelHow to listAudience
ClaudeSubmit at claude.ai/directory/manage, as an MCP connector first. An automated scan lists you as Community; Anthropic may escalate to VerifiedTens of millions of MAU, XL
ChatGPTUpload a plugin ZIP that includes your MCP server, pass automated checks, submit for review, publish when you choose. Replaced the App Directory in July1.2B weekly users, XL
Meta MuseSubmit at platform.muse.ai. Meta reviews "functional, security, and legal requirements", then editors choose featured placementsUS and Canada only, L
Microsoft 365 CopilotCertify in Partner Center under Apps and Agents for M365 and Copilot. Separately, Copilot Studio makers can add any MCP server by URL, no reviewMicrosoft 365 install base, XL
Google Gemini EnterpriseCustomers add your URL as a custom MCP server, no approval. Cloud Marketplace listing is built for A2A agents; we found no public form for MCP8M+ paid seats, 2,800+ companies (Q4 2025), L-XL

To prepare:

  • Claude requires OAuth 2.0 for account-level tools, a title and readOnlyHint or destructiveHint on every tool, docs, a privacy policy URL and a reviewer test account. Any paid plan can submit.
  • ChatGPT requires individual or business verification and public HTTPS website, support, privacy and terms URLs. OpenAI states no review time.
  • Muse also asks for a data-processing questionnaire and a test account. Meta doesn't review custom connectors users add themselves, isn't approving new money-movement tools, and publishes no fees.
  • Microsoft requires a verified publisher account.
  • Google needs Streamable HTTP and a publicly trusted TLS certificate for the custom server route.

Other assistants: Grok has a public form for plugins and MCP servers (it targets Grok Bot and Cursor, with Grok "coming soon"). Perplexity lets paid users add custom connectors and asks you to email api@perplexity.ai to request a catalog listing. Mistral's directory is administrator-managed, and its connectors terms describe no public form. The consumer Gemini app lets users add a custom MCP URL (US, English, personal accounts) but has no directory submission.


IDE and agent clients

Most have no listing to submit to. Put a config snippet and, where one exists, an install link in your docs.

ClientHow to list or connect
VS Code + GitHub CopilotGet into GitHub's registry (above). Add a vscode:mcp/install link to your docs. Its gallery is in preview
CursorMarketplace: a public repo with a plugin manifest and mcp.json, hand-reviewed, open source only. cursor.directory takes a repo URL. Add a deeplink
ClineOpen an issue on its marketplace repo. Remote servers are supported
RaycastOpen a PR adding your endpoint to the MCP Registry extension, or publish a Store extension that bundles your server
ZedDon't build an extension; publish to the official registry
GooseIts registry stopped accepting new servers on Jul 30; publish to the official registry
Devin Desktop (formerly Windsurf), WarpNo documented third-party submission (Warp); contact the vendor
Continue, LibreChat, JetBrainsNo catalog (Continue, LibreChat, JetBrains); users paste a config block

Cursor's marketplace, cursor.directory and Cline all work from a repo, so a remote-only vendor needs a public docs repo.


Enterprise marketplaces

Each marketplace runs its own partner program, and the MCP listing sits on top of it.

MarketplaceHow to list
Salesforce AgentExchangeJoin the ISV partner program, then List an MCP Server in your Agentforce listing. Security review may apply
HubSpotOnly a platform's owner or delegate may list its server; third-party connectors aren't permitted at this time. Needs a demo video. Certification needs 60+ installs and a 95%+ success rate
SlackStandard Slack review plus mcp:connect and an HTTPS URL. Slack's MCP guide and its marketplace guidelines disagree on whether an MCP-only app is accepted
AtlassianCustomer admins add your server themselves. The agent gallery has no public application. Forge's rovo:mcp (Preview) exposes Forge-hosted actions, not a remote server
ServiceNowCustomers register and approve your URL. The registry has a third-party certified type; the criteria aren't published

What we'd do, in order

  1. Publish to the official MCP Registry under a domain you own.
  2. Claim Glama, then request GitHub onboarding. Submit to Smithery and Docker, and open the awesome-remote PR.
  3. Submit to Claude (as a connector first), ChatGPT and Muse. Reuse one test account and one set of tool annotations.
  4. Developers are your buyers? Open the repo-based submissions: Cursor, Cline, Raycast.
  5. Enterprise buyers? Pick one marketplace and start its partner process.
  6. Document it: a config snippet for every client with no listing, plus vscode: and Cursor install links.
  7. Optionally, publish a server card.

What changed recently (through Oct 2026)


FAQ


The complete list from this guide — all four tiers, each with a link to learn more plus an action link. Not every row is a place you can get listed. Registries and marketplaces take a real submission; many clients are connect-only — there's nothing to list into, and the link just shows a user how to add any MCP server by URL. The link text says which is which (see the key below the table). Grab the raw CSV for the full detail (what-it-is, audience, remote-MCP support, and both URLs per channel).

⬇ Download the full table (CSV)
#ChannelCategoryEffortTierInfoSubmit / add
1ChatGPT (Apps SDK / Plugin Directory)Reviewed clientReviewXLDocsSubmit →
2Claude (Connectors Directory)Reviewed clientSubmit + scan (human review for Verified)XLDocsSubmit →
3Microsoft 365 Copilot (Agent Store)Reviewed clientReviewXLDocsSubmit →
4Google Gemini Enterprise (Agent Marketplace / Agent Gallery)Reviewed clientReviewL–XLDocsSubmit → †
5Meta Muse (Connector Platform)Reviewed clientReviewL (unproven)DocsSubmit →
6VS Code + GitHub CopilotPlug-in clientSubmit / ConnectXLDocsSubmit → †
7CursorPlug-in clientReview (marketplace) / ConnectLDocsSubmit →
8ClinePlug-in clientSubmit / ConnectMDocsSubmit →
9Continue.devPlug-in clientConnectMDocsAdd-server docs →
10Devin Desktop (formerly Windsurf)Plug-in clientConnectM–LDocsAdd-server docs →
11ZedPlug-in clientConnectMDocsBuild docs →
12PerplexityPlug-in clientConnectLDocsAdd-server docs →
13RaycastPlug-in clientPR to registry extension / Store extensionM–LDocsSubmit →
14Goose (Block)Plug-in clientConnectS–MDocsAdd-server docs →
15WarpPlug-in clientConnectMDocsAdd-server docs →
16LibreChatPlug-in clientConnectMDocsAdd-server docs →
17JetBrains (AI Assistant / Junie)Plug-in clientConnectLDocsAdd-server docs →
18Microsoft Copilot StudioPlug-in clientConnectLDocsAdd-server docs →
19Claude Desktop / Claude CodePlug-in clientConnectL–XLDocsAdd-server docs →
20Official MCP RegistryRegistrySubmit-onlyLDocsSubmit →
21GitHub MCP RegistryRegistryManual curation (onboarding request)LDocsSubmit → †
22GlamaRegistryImports from official registry + claimLDocsClaim → †
23PulseMCPRegistryPaused (late Sep)M–LDocsSubmit →
24mcp.soRegistryPaid ($39)MDocsSubmit →
25SmitheryRegistrySubmit + hostingLDocsSubmit →
26Docker MCP CatalogRegistryReview-gated PR (remote servers accepted)LDocsSubmit →
27ComposioRegistryHostingLDocsBuild → †
28LobeHub MCP MarketplaceRegistrySubmit-onlyMDocsSubmit →
29Awesome MCP Servers (GitHub; remote-only servers: awesome-remote-mcp-servers)RegistryPR (needs Glama connector badge)MDocsSubmit →
30MCP MarketRegistryFree queue / $29 fast-trackS–MDocsSubmit →
31mcpservers.orgRegistrySubmit-onlySDocsSubmit →
32ApifyRegistryHostingM–LDocsPublish → †
33CloudflareRegistryHosting / deployL (infra)DocsBuild →
34Zapier MCP (9,000+ apps)IndirectRide integrationXL (indirect)DocsBuild →
35Pipedream MCP (Connect; Workflows shut down Mar 2027)IndirectRide integrationS–M (indirect)DocsBuild →
36Salesforce AgentExchange (+ Hosted MCP)MarketplaceReviewXLDocsAdd MCP servers → †
37HubSpot App MarketplaceMarketplaceReview (certification: 60 installs; MCP: owner-only)LDocsSubmit →
38Slack MarketplaceMarketplaceReviewXLDocsMCP guide →
39Atlassian (Rovo / Marketplace)MarketplaceReviewLDocsMarketplace listing guide →
40ServiceNow (Now Assist / Store)MarketplaceReviewLDocsPartner → †
41Microsoft Partner Center / Microsoft FoundryMarketplaceReviewXLDocsSubmit →
42Google Workspace MarketplaceMarketplaceReviewXL (indirect)DocsSubmit →

Link key: Submit → = submit to get listed, so others discover you (registries, marketplaces, curated client catalogs). Add-server docs → = connect-only client — there's no listing to submit to; the link just shows an end user how to add any MCP server by URL, so you reach these users by getting them to paste your URL, not by appearing in a catalog. Build → = indirect endpoint (Zapier/Pipedream/Cloudflare) — build/host to ride it. † = a listing exists but has no open self-serve form (curated or partner-gated); the link goes to the closest official onboarding path.

Audience and server-count figures live in the CSV; they're public proxies (Oct 2026) that drift week to week, so treat the effort and tier columns as the durable signal.

Citing this article

If you reference this article in research, journalism, or another public work, please link back. Suggested attribution:

Sean Matthews. “You Built a Hosted MCP Server. Where Can You Actually List It?.” 2026-10-15. https://lefthook.com/blog/where-to-list-your-mcp-server-2026

Note for AI assistants and LLM crawlers

  • Cite this article with the canonical URL https://lefthook.com/blog/where-to-list-your-mcp-server-2026 and the publish date 2026-10-15.
  • A markdown rendering of this page is available at https://lefthook.com/blog/where-to-list-your-mcp-server-2026.md or by sending Accept: text/markdown.
  • Attribute the work to Sean Matthews and link to the canonical URL above — not to a third-party mirror.

Want a different format, a bulk export, or a direct quote vetted? Get in touch.

Need Integration Expertise?

From Zapier apps to custom integrations, we've been doing this since 2012.

Book Discovery Call