# Install mcp-publisher with Homebrew Publisher CLI tool for the Official Model Context Protocol (MCP) Registry. Version 1.7.9 via Homebrew; verified 2026-05-13. ## Install ```sh sudo av install brew:mcp-publisher ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install mcp-publisher ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:mcp-publisher - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.7.9 - **Source summary:** Publisher CLI tool for the Official Model Context Protocol (MCP) Registry - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-05-13T00:18:47Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - mcp-publisher (cli) - mcp-publisher (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.7.9 - Package-manager updated: 2026-05-13 - Local data: ok - Upstream repository: https://github.com/modelcontextprotocol/registry - Upstream latest detected: v1.7.9 (current) ## Project history and usage mcp-publisher is the official CLI used to publish server metadata to the Model Context Protocol Registry. It lives in the modelcontextprotocol/registry repository alongside the registry service and documentation. ### 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 - - - - - - source_facts.repo ## Security Notes No matching local secret-handling manifest was found for mcp-publisher. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** mcp-publisher - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Package publisher tools](https://www.automicvault.com/pkg/package-publishers/) - Belongs to a package publishing or registry command family. - [MCP tool packages](https://www.automicvault.com/pkg/mcp-tools/) - Mentions MCP or Model Context Protocol. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [airtable-mcp-server](https://www.automicvault.com/pkg/brew/airtable-mcp-server/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [chrome-devtools-mcp](https://www.automicvault.com/pkg/brew/chrome-devtools-mcp/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [docker-ls](https://www.automicvault.com/pkg/brew/docker-ls/) - Shares av.db curated category or tags: cli, developer-tools, registry. - [mcp-get](https://www.automicvault.com/pkg/brew/mcp-get/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [mcp-inspector](https://www.automicvault.com/pkg/brew/mcp-inspector/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [mcp-remote](https://www.automicvault.com/pkg/brew/mcp-remote/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [mcphost](https://www.automicvault.com/pkg/brew/mcphost/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [mcpm](https://www.automicvault.com/pkg/brew/mcpm/) - Shares av.db curated category or tags: cli, developer-tools, mcp. - [mcp-atlassian](https://www.automicvault.com/pkg/brew/mcp-atlassian/) - Package names and metadata indicate a similar tool family. Shared terms: cli, developer, developer-tools, mcp, server. ## Combined YAML source View the package source record on GitHub. [combined/mcp-publisher.yml](https://github.com/automic-vault/db/blob/main/combined/mcp-publisher.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph