MCP Registry CLI
The official MCP server registry and the mcp-publisher tool for publishing your own server
- 7,418 ★ on the repository
- Last commit
Extended access
Why this level
- Publishes server metadata to a public registry on behalf of your GitHub account or domain
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/mcp-registryDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Publishes server metadata to a public registry on behalf of your GitHub account or domain
This is third-party code. Review the repository files before installing.
What it does
The repository holds the registry service, which serves MCP clients a server list via an API, and the mcp-publisher tool. A server author generates a server.json template with mcp-publisher init, signs in via GitHub and publishes with mcp-publisher publish. The registry verifies namespace ownership through a GitHub account, GitHub Actions OIDC, or DNS or HTTP domain verification. The service can be self-hosted from a Docker image.
Who it is for. For MCP server authors and client developers who need a server directory.
Good fit when
- You want to publish your MCP server to the official registry
- You need to fetch MCP servers via API in your client
- You want to run a private registry inside your company
Not a fit when
- You only want to find and connect a server, not publish one
- Your server is not available via npm, PyPI, Docker or a URL
Example request
Prepare server.json for my MCP server and publish it to the MCP registryLimitations
The registry is in preview: the v0.1 API is frozen, but changes and data resets may happen before general availability. Publishing requires proving namespace ownership via GitHub or a domain. Building from source needs Go, Docker and ko.
How to disable. Remove the tool with brew uninstall mcp-publisher or delete the binary from /usr/local/bin.
FAQ
How should the server be named?
The name is tied to a namespace: io.github.username for GitHub sign-in, or your domain in reverse notation.
Where is the API documented?
Live API docs are at registry.modelcontextprotocol.io/docs.
Discussion
No questions or reviews yet.
Related
CLI toolsReference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything
A plugin with skills for building TypeScript MCP servers and MCP apps: the agent scaffolds, edits, debugs and verifies them
Docs MCP Server
Grounded Docs MCP Server
A local MCP server that indexes docs from websites, GitHub, npm, PyPI and files and gives the agent version-aware search
A remote MCP server that gives the agent docs and code of any public GitHub repository with nothing to install
Cocos Creator MCP Server
Cocos Creator MCP Server Plugin
An MCP server as a Cocos Creator editor extension: the agent controls scenes, nodes, components, prefabs and project assets
A fast MCP server in Rust extended with WebAssembly plugins: plugins load from OCI, files, http(s) and s3, and OCI signatures can be verified
README in short
The README covers project status, the working group and running locally with make dev-compose and PostgreSQL. It describes prebuilt Docker images, building mcp-publisher and the code layout. The auth section explains how namespace ownership is verified. The publishing guide lives separately in docs.