Remote server
Remote MCP is recommended for external coding clients. No Murmur CLI needed. Add this URL to any client that supports Streamable HTTP MCP servers:1
Add the server
2
Sign in
Sign in when your client prompts, or start it yourself with
claude mcp login murmur or codex mcp login murmur. In the browser, sign in with GitHub, choose your organization, and select Allow access. Your client keeps the token.Local server
Use local MCP for direct file access, catalog writes from files, or VM port URLs. The local server runsmurmur mcp on your machine; Murmur agent VMs configure it automatically.
1
Install the Murmur CLI and sign in
Follow CLI through
murmur login.2
Register the server
How the local and remote servers differ
How the local and remote servers differ
Local MCP adds direct file access (
upload, catalog_set, and catalog_get.out) and VM port_url. Remote MCP supports attachments through prepare_attachments followed by client-side HTTP uploads, and exposes trigger_flight. See the capability comparison.Connect as a service profile
For CI jobs and hosted platforms with no browser, use a service profile API key instead of signing in: sendAuthorization: Bearer <key> to the remote URL. Local MCP reads the key from MURMUR_API_KEY. Tools then act as the service profile. See API keys.
Give agents other MCP servers
Connecting a client to Murmur doesn’t give agents any new tools. To give agents tools from another MCP server, install it as a plugin:- Add the server’s
.mcp.jsonto a plugin marketplace repo in your GitHub organization. - Store its token as a secret.
- Add the plugin and the secret to a workspace. Its agents start with the server’s tools.