# 使用 Homebrew 安装 mcp-publisher 查看 mcp-publisher 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:mcp-publisher ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install mcp-publisher ``` 证据: local Homebrew formula metadata ## 软件包事实 - **软件包键:** brew:mcp-publisher - **软件包管理器:** Homebrew - **版本:** 1.8.0 - **来源摘要:** Publisher CLI tool for the Official Model Context Protocol (MCP) Registry - **主页:** - **仓库:** - **最后更新:** 2026-07-29T17:04:52+02:00 - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - mcp-publisher (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 1.8.0 ## 项目历史与用法 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. ### 项目历史 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. ### 采用历史 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. ### 使用方式 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. ### 为什么软件包爱好者会关心 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. ### 时间线 - 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. ### 来源 - - - - - - source_facts.repo ## 安全说明 没有找到 mcp-publisher 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布，以便未来覆盖拥有稳定的软件包 URL。 ## Combined YAML source View the package source record on GitHub. [combined/mcp-publisher.yml](https://github.com/mxcl/pkgdb/blob/main/combined/mcp-publisher.yml) ## 来源 - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph