mcpm

mcpm is a command-line tool that manages MCP servers within Claude App and can itself run as an MCP server. The CLI provides commands to search for MCP packages, install them, and manage a collection of MCP servers (add, remove, enable, disable, list). You can also start the mcpm CLI as an MCP server with the mcp subcommand, enabling Claude to treat the mcpm instance as just another MCP server. Use the search and install features to discover community MCP packages, then deploy them to your Claude App with a few keystrokes. When started as an MCP server, mcpm exposes management capabilities through Claude’s MCP interface, allowing you to monitor and control server instances from within Claude App.

Prerequisites:

• Node.js and npm installed on the system where Claude App runs
• Access to install global npm packages or run npx commands

Installation steps:

1. Install the MCPM CLI globally (or use npx to run it without permanent install):

npm install -g @mcpm/cli

2. Verify installation:

mcpm --version

3. Start using mcpm to manage MCP servers, or start it as an MCP server within Claude App:

# Start the CLI to manage servers
mcpm

# Start mcpm as an MCP server (within Claude App context)
mcpm mcp

Notes:

• The mcpm CLI can be executed directly as a CLI or via npx to avoid a global install.
• Ensure Claude App is properly configured and has access to the filesystem paths used by mcpm for storage and configuration.

Tips and common issues:

• When using npm install -g @mcpm/cli, ensure your shell's PATH includes the global npm bin directory.
• Disabled MCP servers are stored in Claude App's storage; active servers live in Claude App's configuration.
• If mcpm cannot start as an MCP server, check that the Node.js environment is available to Claude App and that the CLI has the necessary permissions to bind to any required ports.
• You can update mcpm by reinstalling the CLI or using your package manager if you installed it globally. For local runs via npx, you’ll fetch the latest version automatically.
• Environment variables are generally not required but may be used for integration or custom storage paths; consult the official docs for any package-specific env vars.