Install mcpm with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• mcpm

Project history

The public GitHub repository was created in March 2025 by Path Integral Institute. The official README calls the project MCPM - Model Context Protocol Manager and describes it as an open-source CLI that provides a simplified global configuration approach for MCP servers.

The project moved from an earlier target-based model to a v2.0 global workspace model. Its README says MCPM v2.0 installs servers once, organizes them with profiles, integrates them into clients, and includes a central registry for discovering available MCP servers.

Adoption history

By July 2026, the repository had just under 1k GitHub stars and more than 100 forks. Its official website markets it as a modern MCP server manager and says it works with any MCP client by configuring servers to use `mcpm run server-name`.

The supported-client list on the website and README includes Claude Desktop, Claude Code, Cursor, Windsurf, VSCode, Continue, Cline, Roo Code, OpenCode, Goose CLI, Gemini CLI, Codex CLI, and others. That breadth is the project's adoption pitch: one package-manager-like layer spanning many MCP consumers.

How it is used

The core package workflow is package-manager-shaped: `mcpm search`, `mcpm install SERVER_NAME`, `mcpm ls`, `mcpm update`, and `mcpm uninstall`. Users can also create profiles, run all servers in a profile, share servers through tunnels, import client configurations, and edit client integrations.

The README documents non-interactive environment variables such as `MCPM_NON_INTERACTIVE`, `MCPM_FORCE`, and `MCPM_JSON_OUTPUT`, plus an `llm.txt` guide intended for AI agents. That makes MCPM notable as both a human CLI and an automation surface for agents managing their own MCP server environment.

Why package nerds care

MCPM is package-nerd significant because it explicitly imports package-manager concepts into MCP: a registry, install/uninstall commands, global state, update checks, profiles, and client adapters. It exists because installing MCP servers by hand in every client config quickly becomes repetitive.

It also illustrates the MCP ecosystem's registry problem. As MCP servers multiplied, a dedicated manager became useful not just for installation, but for knowing which client configs point to which server definitions and for keeping those definitions portable across tools.

Timeline

• 2025-03: Public GitHub repository created.
• 2025-03: v1.0.1 release published.
• 2025-2026: Project documents a v2.0 global workspace model replacing earlier target-based configuration.
• 2026-05: v2.15.0 release published.

Related projects

• MCPM is related to MCP clients such as Claude Desktop, Claude Code, Cursor, Gemini CLI, Codex CLI, and Goose. Within MCP package tooling it complements mcptools, which inspects and calls MCP servers, and MCPHost, which hosts model interactions with configured MCP tools.

Sources

• https://api.github.com/repos/pathintegral-institute/mcpm.sh
• https://api.github.com/repos/pathintegral-institute/mcpm.sh/releases
• https://github.com/pathintegral-institute/mcpm.sh
• https://mcpm.sh/