Publish to the Official MCP Registry Checklist
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.
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.
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.