Publish an MCP Server to the Registry
The official quickstart uses the mcp-publisher CLI. The registry stores metadata, so package-based local servers first need to publish their actual artifact to the relevant package registry.
Typical flow
- Choose a verified server namespace/name.
- Publish the package/artifact.
- Create and validate
server.json. - Authenticate
mcp-publisher. - Run
mcp-publisher publish. - Query the Registry to verify the release.
Authentication choices
The Registry supports methods including GitHub-backed identity and DNS-based verification. Your namespace must match the ownership verification method.