Disclosure: GearPicked is reader-supported. Some links on this page are affiliate links; if you buy through them we may earn a commission at no extra cost to you. This never changes what we recommend. As an Amazon Associate, GearPicked earns from qualifying purchases. Read our affiliate disclosure.

Where to Submit Your MCP Server: Registry vs Directories

By Balwant Singh Rawat · Published 8 November 2026 · Updated 8 November 2026· Research-based (not yet hands-on tested)

Last checked: 8 November 2026 (IST). This is a comparison of the routes described on the operators’ own pages, not a hands-on test of publishing a server. No submission was made for this research. Requirements can change; follow the linked source before publishing.

Quick answer: start with the official MCP Registry for machine-readable metadata, then choose community listings that match your distribution goal. Use a client connector submission only if you want that client’s in-product discovery and can meet its requirements. A server can be technically installable without being listed in any marketplace.

MCP registry vs directory vs connector review

These three tasks are often called “submit my MCP,” but the deliverables are different:

A directory may also offer hosting or a gateway. That is a separate service from a listing. Do not deploy a server or buy hosting merely because you wanted a public profile.

Official MCP Registry: publish metadata, not an advert

The official quickstart shows an npm-based TypeScript example. The Registry hosts metadata, not your package artifacts. Its docs still describe the service as preview at the time of this check.

For the npm route:

1. Choose the correct namespace. With GitHub authentication, names use io.github.username/server or the supported organization namespace. Other authentication methods have different namespace rules; read the authentication documentation.
2. Add mcpName to your package metadata. It must match the name in server.json.
3. Build and publish the underlying package to npm first. Confirm the version can be retrieved publicly.
4. Install the official mcp-publisher using the installation instructions in the quickstart. Run mcp-publisher init, then review the generated server.json: package identifier, version, transport and required environment variables.
5. Authenticate with the method matching your namespace; the GitHub example uses mcp-publisher login github. Review the actual authorization screen yourself.
6. Run mcp-publisher publish. Verify the result through the Registry’s search/API, not just the terminal receipt. The quickstart shows https://registry.modelcontextprotocol.io/v0.1/servers?search=YOUR_SERVER_NAME.

Remote-only server? Do not copy the npm prerequisite blindly. The remote server documentation supports a remotes entry in server.json, including a transport type and endpoint URL. The endpoint must be publicly reachable. Streamable HTTP is recommended; SSE is deprecated for new integrations. Publicly reachable does not mean every tool must be usable without authentication: declare the authentication requirements accurately.

Never place real API keys in public metadata, a README, screenshots or listing descriptions. Declare required secrets as configuration requirements, not secret values. Publishing metadata does not test every tool’s safety or mean that users have granted permission for your server’s actions.

Community MCP directories: checked routes

We checked four community operators, including one currently paused. These are not partners, endorsements or a recommendation to pay. We did not independently verify their audience, authority-score or dofollow claims.

Glama: repository indexing and hosted connectors are distinct

Glama’s FAQ also describes a separate remote connector route: connectors page → Add Server → Hosted endpoint. Supply a name, description and HTTPS Streamable HTTP endpoint. Only healthy connectors are indexed; unhealthy ones remain pending. Configure any private test credentials in the test profile, never in public listing fields.

For repository ownership, Glama documents glama.json: add the metadata file at the repository root with your GitHub maintainer identity, then use the claim flow to sync it. Its ownership article distinguishes personal repositories from organization-owned repositories. Ownership evidence is not the same as a favorable security rating.

Client connector review is a separate submission

For example, the current Claude connector submission instructions direct authors to the developer portal at claude.ai/directory/manage, select Submit new, then MCP connector. The requirements include:

• A remote HTTPS endpoint and working authentication: OAuth 2.0 for authenticated services or no authentication for public-data tools, according to the applicable docs.
• Tool titles and the applicable read-only or destructive annotations.
• Documentation, privacy policy, support contact, icon and use-case information.
• Testing every tool and supplying appropriate reviewer test access through the portal, not publicly.
• A paid Claude plan for submitting through the portal. This is not a universally free distribution route.

The page says compliant submissions are scanned and, by default, listed as Community connectors; some receive human review, with variable queues. Per-customer URL options require Verified status before publication. Local servers are not accepted as standalone MCPB submissions; the documented distribution path is a plugin. Read the live policy rather than relying on older tutorials. A community label, verification label and registry record are different things.

MCP submission checklist: prepare once, adapt by route

Use this checklist before opening any form:

1. Choose the object being listed: installable package, hosted MCP endpoint, agent, or the product website. Do not paste a marketing homepage where a protocol endpoint is required.
2. Prove ownership: correct GitHub user/organization or domain namespace; consistent repository, package metadata and maintainer identity.
3. Make setup reproducible: supported transport, exact install command/version, required configuration names and clear prerequisites. Test the documented path from a clean client.
4. Describe the actual tools: what each reads, writes or deletes; necessary permissions; authentication, rate limits and any billable operations. Separate claims from tested behavior.
5. Prepare public materials: short description, useful task examples, README, license, docs, pricing/access limits, privacy policy, logo and support route.
6. Protect reviewer access: dedicated least-privilege test account with no live customer data. Submit any test secret only through the operator’s private review mechanism.
7. Check commercial conditions: free listing or paid publishing? Required badge or reciprocal link? Queue estimate or no stated deadline? Stop if the conditions do not fit your launch policy.
8. Record evidence separately: submitted timestamp, namespace/version or listing ID, receipt, published URL, health/review status and next check. A receipt is not proof of publication.

If publication fails, repair the relevant layer: package ownership or metadata for the Registry; endpoint health for connector indexing; eligibility or editorial materials for a marketing listing. Submitting the same incorrect record everywhere does not solve the underlying problem.

Which route should a founder do first?

• Open-source local server: publish its package and Registry metadata; then evaluate Glama’s repository route and other community listings.
• Hosted remote server: publish accurate remote metadata; check endpoint health; evaluate community connector indexing and any client-specific review.
• An AI product with an MCP integration: technical listings can explain the integration. Separately list the actual product in relevant AI-agent directories; do not represent the product homepage as an MCP server.

For broader launch preparation, read how to submit an AI tool to directories and our checked free AI/SaaS directory options.

Disclosure and scope: GearPicked publishes this DIY guide and sells a manual product/website directory submission service. That is not an offer of MCP Registry publishing, connector engineering, security certification or client-directory approval. Eligibility, publication, backlinks, indexing and rankings are never guaranteed.