Skip to content

Claude's directory portal is open →

Publishing to the MCP Registry

How do you publish an MCP server to the Official MCP Registry?

Describe the server in a server.json whose remotes property lists its public URL, then authenticate the namespace you publish under: GitHub for io.github.* names, or DNS or HTTP for a domain you control. The registry is still in preview, so breaking changes or data resets may happen before general availability. Invokary tracks each rule with its source.

You publish a remote MCP server to the official MCP Registry with a server.json whose remotes list its public endpoint, under a namespace you authenticate: GitHub for io.github.* names, or DNS or HTTP for your own domain. The registry is in preview, so breaking changes or data resets can still happen.

Below is each requirement we track, with its source and the date we last checked it.

Reviewed by Mohd. Ashhar · Last verified:

Invokary is an independent studio. We are not affiliated with or endorsed by Anthropic, OpenAI or Anysphere.

Steps to get listed

In order, each step linked to the requirement it comes from.
  1. Make the server publicly accessible at its remote URL.
  2. Write a server.json whose remotes property lists that URL.
  3. Authenticate your namespace: GitHub for io.github.* names, DNS or HTTP for a domain you control.
  4. Publish, and keep an eye on the registry while it is in preview: breaking changes or data resets may happen.

The platform decides whether to list your connector or plugin and where it appears. We can't guarantee either.

We went through this with our own server

We published our own MCP server to the registry on October 5, 2026, as com.invokary/platform-requirements. We authenticated the com.invokary namespace over HTTP, with a public key served at invokary.com/.well-known/mcp-registry-auth, then published its server.json with the registry's mcp-publisher tool.

See our server and where it is listed

Requirements

Each requirement shows where it comes from and when we last checked it.

Submission

  • A remote server is published with a server.json whose remotes property lists its URL, and the server must be publicly accessible there.

    Official sourceSource: MCP Registry: Publishing remote serversChecked

Who can submit

Limits

What changed

No changes logged for this platform yet.

All platform changes

Find out where you stand in five days.

$750. Credited in full to your build.

Book a $750 Audit