Agent MCP Directory

Get listed in each MCP registry

Publish once to the official registry and submit where review applies, with what each one checks. In the directory, 493 companies are in the official registry and 504 in the GitHub registry. First step: Official registry: mcp-publisher with GitHub, DNS or HTTP namespace proof.

Steps

  1. Official registry: mcp-publisher with GitHub, DNS or HTTP namespace proof.
  2. Claude Connectors Directory: developer portal, annotations, OAuth.
  3. GitHub MCP Registry: check your listing through the API.
  4. Glama: Add Server; claim your listing.

What the sources say

  • Publishing to the official registry uses the mcp-publisher CLI; pull requests do not list servers. (github.com, read 4 November 2026)
  • Reverse-DNS namespaces need DNS or HTTP proof; io.github.<user>/ needs that GitHub login. (github.com, read 4 November 2026)
  • Claude Connectors Directory needs a remote HTTPS URL, OAuth 2.0 for user data and title plus readOnlyHint or destructiveHint on every tool. (claude.com, read 4 November 2026)
  • The GitHub MCP Registry API at api.mcp.github.com/v0/servers answered without a key on 4 Nov 2026 and listed 773 entries. (api.mcp.github.com, read 4 November 2026)
  • Glama lets anyone add a server; 10,287 of 115,804 listings were claimed on 4 Nov 2026. (glama.ai, read 4 November 2026)

Registries compared on submission

RegistryHow a server gets inDiscoverability
Smitheryunclear after acquisitioncatalog browse only
Glamaopen, Add Server buttonAPI with key and attribution
Official MCP RegistryCLI with namespace verificationopen paginated API
GitHub MCP Registrynot documented on the pageopen API and install buttons
Claude Connectors Directoryportal, automated scan, optional human reviewinside Claude

Directory companies listed: 493 in the official MCP Registry, 504 in the GitHub MCP Registry and 117 in the awesome-remote-mcp-servers list.

A listing is only part of discovery; a server card tells an agent what the server is before it connects.