Skip to content

docs: explain publishing community servers to the MCP Registry #4726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CryoThrust wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −0
Open

docs: explain publishing community servers to the MCP Registry #4726

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,6 +137,19 @@ On Windows, apply the same wrapper to each `npx`-based entry above by changing `

Interested in creating your own MCP server? Visit the official documentation at [modelcontextprotocol.io](https://modelcontextprotocol.io/introduction) for comprehensive guides, best practices, and technical details on implementing MCP servers.

### Publishing a Community Server

Community-built servers should be published to the [MCP Registry](https://registry.modelcontextprotocol.io/), rather than added to this reference-server repository. The Registry stores server metadata and points clients to the package or container that you publish separately.

The usual publishing flow is:

1. Publish and test your server artifact (for example, an npm package or an OCI image).
2. Add the Registry identity and artifact details to a `server.json` manifest. For GitHub-authenticated publishing, the manifest name must use the `io.github.<account>/...` namespace.
3. Install [`mcp-publisher`](https://github.com/modelcontextprotocol/registry), then run `mcp-publisher validate` locally.
4. Authenticate with `mcp-publisher login` and publish with `mcp-publisher publish`.

See the [Registry publishing quickstart](https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx) for the current manifest schema, package-specific ownership checks, and supported authentication methods. Registry publication does not require a pull request to this repository; use this repository's issue tracker for problems with the reference implementations themselves.

## 📚 Learn More

See [ADDITIONAL.md](ADDITIONAL.md) for a curated list of frameworks and resources that simplify building MCP servers and clients.
Expand Down
Loading