mpak run
Run an MCP server directly from the registry. Bundles are cached locally for fast subsequent runs.
mpak run <package>Examples
Section titled “Examples”# Run latest versionmpak run @nimblebraininc/echo
# Run specific versionmpak run @nimblebraininc/echo@1.0.0
# Force re-download (update cache)mpak run @nimblebraininc/echo --update
# Run a local .mcpb bundle filempak run --local ./path/to/bundle.mcpbOptions
Section titled “Options”| Option | Description |
|---|---|
--update | Force re-download even if cached |
-l, --local <path> | Run a local .mcpb bundle file instead of fetching from the registry |
How It Works
Section titled “How It Works”- Check cache - Look for bundle in
~/.mpak/cache/ - Download - If not cached (or
--update), download from registry - Extract - Unzip the
.mcpbfile - Run - Execute the server using the bundled configuration
The server runs in the foreground, communicating via stdio (JSON-RPC).
Integration with Claude
Section titled “Integration with Claude”See the Integrations section for setting up mpak bundles with:
- Claude Code - One command:
claude mcp add --transport stdio echo -- mpak run @nimblebraininc/echo - Claude Desktop - JSON config file
Configuration
Section titled “Configuration”Some bundles require configuration (API keys, etc.). See mpak config for storing configuration values.
Troubleshooting
Section titled “Troubleshooting”Bundle not found
Section titled “Bundle not found”Error: No bundle found for @owner/package on darwin-arm64The bundle may not be available for your platform. Check available platforms with mpak bundle show.
Python not found
Section titled “Python not found”Error: python3 not foundPython-based bundles require Python 3.10+ to be installed and available in your PATH.