Get the FREE Ultimate OpenClaw Setup Guide →

mcpm.sh

CLI MCP package manager & registry for all platforms and all clients. Search & configure MCP servers. Advanced Router & Profile features.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio pathintegral-institute-mcpm.sh bash -lc mcpm.sh \
  --env MCPM_REGISTRY_URL="Registry URL for MCP servers (default https://mcpm.sh/registry)"

How to use

MCPM is a CLI tool that centralizes management of MCP servers. With the mcpm.sh server entry, you can leverage MCPM to install, organize, and run MCP servers locally, and optionally expose them over HTTP or via secure tunnels for testing or remote access. This server represents the MCPM client/tool itself in the MCP ecosystem, enabling you to manage your MCP environment from a single interface and to integrate it with other MCP clients like Claude Desktop, Cursor, Windsurf, and more. Use MCPM to search the registry, install a server globally, group servers into profiles, and run them directly over stdio or HTTP for quick testing. The tooling also supports non-interactive automation and provides an llm.txt guide to assist AI agents in using the CLI effectively.

How to install

Prerequisites:

  • A Unix-like system (Linux/macOS) or Windows with WSL
  • curl or wget
  • Node.js not required for mcpm.sh if using the provided install method
  1. Install MCPM using the official install script:
curl -sSL https://mcpm.sh/install | bash
  1. Verify installation:
mcpm --version
  1. Initialize or configure registry access (if needed):
export MCPM_REGISTRY_URL=https://mcpm.sh/registry
  1. Add the mcpm.sh server to MCPM (example workflow):
mcpm new mcpm.sh --type stdio --command "mcpm.sh" --args "--help"
  1. Install the server globally from the registry (example):
mcpm install mcpm.sh
  1. Run the server directly for testing:
mcpm run mcpm.sh

Note: The mcpm.sh server entry represents the MCPM client/tool itself; you can adapt the command/arguments to your environment if mcpm.sh provides a different invocation mode.

Additional notes

Tips and common considerations:

  • MCPM supports both stdio and HTTP execution modes. Use --http when you need to expose a server via HTTP for testing or automation.
  • For automation, set MCPM_NON_INTERACTIVE, MCPM_FORCE, and MCPM_JSON_OUTPUT environment variables as described in the CLI docs.
  • If you encounter issues connecting to the registry, ensure MCPM_REGISTRY_URL is reachable and correctly configured.
  • Profiles allow you to group multiple MCP servers; combine this with sharing or inspector tools for streamlined testing and debugging.
  • Since mcpm.sh is a CLI-oriented server, ensure your shell environment has the necessary permissions to execute scripts and bind to local ports if you enable HTTP exposure.

Related MCP Servers

Sponsor this space

Reach thousands of developers ↗