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

  1. Choose a verified server namespace/name.
  2. Publish the package/artifact.
  3. Create and validate server.json.
  4. Authenticate mcp-publisher.
  5. Run mcp-publisher publish.
  6. 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.

Reference

Registry publishing quickstart