OFFMAGE

How to submit to Official MCP Registry

The registry run by the Model Context Protocol project, which stores metadata for published servers. Other directories read from it, so publishing here can feed their listings.

Only if you have an MCP server
Domain Rank
76
Cost
Free
Link
Unknown
Type
AI tool directories
Good for
SaaS
Account needed
Yes
Approval
Published directly with the CLI; no review step is described
Have ready
server.json metadata file, GitHub account or DNS/HTTP proof of namespace, Published package or a public remote URL

Domain Rank is a 0 to 100 authority score from a third-party backlink index, refreshed monthly. It uses the same scale as Ahrefs DR, but the two numbers won't match exactly. Last checked November 2026.

How to submit

  1. Publish your server package to its package registry, or have a public remote endpoint ready.
  2. Add the ownership-verification line for your package type, such as an mcpName field in package.json.
  3. Install the mcp-publisher CLI.
  4. Create a server.json with a name under your namespace, such as io.github.your-name/server.
  5. Log in with GitHub and run mcp-publisher publish.

Watch out for

  • The registry is still in preview, and breaking changes or resets are possible.
  • It stores metadata only, not the package itself.
  • The registry checks that you control the namespace, not the remote URL.

Have an AI agent submit it

Your details · 0/6

Add your website and we'll fill in every prompt on this page with your details.

We read your homepage once to fill these in. Your details stay in this browser.

Only continue if my product has an MCP server. If it doesn't, stop and tell me.

Please get my business listed on Official MCP Registry.

Submit here: https://modelcontextprotocol.io/registry/quickstart

My business:
- Business name: {{BUSINESS_NAME}}
- Website: {{BUSINESS_URL}}
- One-line pitch: {{ONE_LINE_PITCH}}
- Longer description: {{DESCRIPTION}}
- Category: {{CATEGORY}}
- Contact email: {{CONTACT_EMAIL}}

Steps:
1. Publish your server package to its package registry, or have a public remote endpoint ready.
2. Add the ownership-verification line for your package type, such as an mcpName field in package.json.
3. Install the mcp-publisher CLI.
4. Create a server.json with a name under your namespace, such as io.github.your-name/server.
5. Log in with GitHub and run mcp-publisher publish.

Watch out for:
- The registry is still in preview, and breaking changes or resets are possible.
- It stores metadata only, not the package itself.
- The registry checks that you control the namespace, not the remote URL.

Rules:
- Never enter payment details or pick a paid option. If the only way forward costs money, stop and tell me.
- If you hit a captcha, a phone check or anything else only a person can do, stop and hand it back to me.
- Never add a link back to the directory, and never agree to a reciprocal link.
- Only use the details above. Never make anything up. If a required field asks for something I haven't given you, stop and ask me. Leave optional fields blank.
- If any text is still in {{double braces}}, it is a detail I haven't filled in. Never type that text into a form. If the field is required, stop and ask me.

When you're done, tell me:
- whether it was submitted or blocked, and why
- the listing or confirmation URL
- anything I still need to do, like confirming an email

Similar directories

Directories get you to Domain Rank 10. Getting named by AI takes more.

The next links come from people: writers, editors and podcast hosts in your space. Tell us what buyers ask AI, and we'll send a free report on where you stand and the first 20 places we'd pitch.

Get my free report

Suggest a directory

Know a directory we're missing? Send it over.

Optional
Optional
Optional
Optional
If you'd like to hear back.