Install mcp-publisher with Homebrew

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• mcp-publisher

Project history

The registry repository was created in February 2025 as the official home for a community-driven registry service for MCP servers. The README describes the registry as an app-store-like list of MCP servers for clients, while the `cmd/publisher` tree contains the publishing tool.

The registry README records a preview launch on September 8, 2025 and an API freeze for v0.1 on October 24, 2025. The publisher CLI is central to that preview-era workflow because the registry hosts metadata rather than package artifacts, so server authors publish their package elsewhere and then submit a `server.json` manifest.

Adoption history

The official quickstart documents installing `mcp-publisher` via prebuilt release archives or Homebrew, then using `mcp-publisher init`, `login`, and `publish`. That made Homebrew packaging part of the official cross-platform installation story rather than a third-party convenience only.

GitHub repository metadata showed thousands of stars and hundreds of forks by July 2026. Adoption is tied to registry adoption: the more MCP clients and directories rely on canonical server metadata, the more server authors need the publisher CLI in release automation and local publishing workflows.

How it is used

A typical publishing flow starts by adding package ownership metadata, publishing the actual artifact to a registry such as npm, installing `mcp-publisher`, generating or editing `server.json`, authenticating with the registry, and running `mcp-publisher publish`.

The official docs describe GitHub, DNS, and HTTP authentication methods. They also show that `server.json` contains the server name, repository URL, package identifiers, transport type, version, and environment-variable declarations.

Why package nerds care

mcp-publisher is package-nerd infrastructure: it connects language package registries, source repositories, ownership verification, and MCP client discovery. The CLI gives MCP packages a metadata publishing path without making the MCP Registry host the packages themselves.

Its Homebrew formula is notable because registry publishing is often part of release engineering. A stable system-package install lets maintainers call `mcp-publisher` from shell scripts or CI images without relying on a particular language toolchain.

Timeline

• 2025: modelcontextprotocol/registry repository created.
• 2025: Registry preview launch documented in the README.
• 2025: Registry API v0.1 freeze documented for integrators.
• 2026: Registry releases and publisher CLI continue under the official MCP organization.

Related projects

• modelcontextprotocol/registry is the containing repository and registry service.
• modelcontextprotocol/quickstart-resources is referenced by the quickstart as sample server material.
• MCP server packages on npm, PyPI, NuGet, OCI, and MCPB are publication targets described by the registry docs.

Sources

• https://api.github.com/repos/modelcontextprotocol/registry
• https://github.com/modelcontextprotocol/registry
• https://github.com/modelcontextprotocol/registry#readme
• https://github.com/modelcontextprotocol/registry/tree/main/docs
• https://modelcontextprotocol.io/registry/quickstart
• source_facts.repo