![Publish to the Official MCP Registry Checklist](https://cdn.slatesource.com/9/1/2/91250f36-8ba8-42dd-92ce-2ffa7790cede.webp)

# Publish to the Official MCP Registry Checklist

- [Made in Slatesource](https://slatesource.com/@mcplisted/publish-to-the-official-mcp-registry-checklist)
- By [mcplisted](https://slatesource.com/@mcplisted)
- Business & Finance
- Created on Nov 13, 2026

## Before you publish to the MCP Registry

Publishing to the official MCP Registry fails for small reasons. This checklist follows the official quickstart, read 2026-11-12. The registry is in preview, so details can change. Recheck the source page.

Seven checks, in order

The server is public: an npm or PyPI package, a public container image, or a public remote URL

npm package: package.json has an mcpName field starting io.github.yourname/

mcp-publisher is installed (Homebrew or the release binary)

You ran mcp-publisher init and edited the generated server.json

The description in server.json is 100 characters or fewer

You ran mcp-publisher login github

You ran mcp-publisher publish

Remote only servers can skip the package steps. The registry checks that you own the server name, not the remote URL. Private servers are not supported.

[Official quickstart: publish to the MCP Registry](https://modelcontextprotocol.io/registry/quickstart?utm_source=slatesource)

[Registry source and issue tracker, look here if publishing fails](https://github.com/modelcontextprotocol/registry?utm_source=slatesource)

## Published, now what?

The registry is one place. Other directories take free submissions too, and one of the big ones is closed right now. See the checked list of where to publish and find MCP servers.

[MCP Server Directory: official pages, checked 2026-11-12](https://slt.social/39KeiAR?utm_source=slatesource)

Want a free listing too?

Send the server name, what it does in one line, and its public registry or repo link. We list public servers only.