Starts the Murmur MCP server, a stdio-based JSON-RPC 2.0 server that exposes agent operations as tools to Claude Code via the Model Context Protocol. This is the primary interface for agent-to-agent orchestration — spawning child agents, monitoring progress, managing tasks, and receiving real-time events. On agent VMs,Documentation Index
Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
Use this file to discover all available pages before exploring further.
murmur mcp is auto-configured at boot. murmur setup registers it for you on local machines when you accept the MCP prompt. To register it manually, run:
Synopsis
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
--debug | bool | no | Log all JSON-RPC stdin/stdout traffic to ~/.murmur/mcp.log. Default: false. |
--workspace | string | no | Workspace name. Overrides the value from murmur.yaml. |
Behavior
The server reads JSON-RPC requests from stdin and writes responses to stdout. It runs until the input stream closes or the process receivesSIGINT or SIGTERM.
On startup, the server performs a version check against the API and prints any upgrade warnings to stderr — never to stdout, which is reserved for the JSON-RPC transport.
Real-time events
The MCP server pushes real-time events to the Claude Code session via theclaude/channel capability. Events include PR comments, CI results, file changes, child agent lifecycle transitions, and notifications from humans or director agents. Events arrive automatically, no polling is required.
Tools exposed
The server exposes all MCP tools — includingspawn, status, ls, kill, wait, upload, task_create, task_update, task_list, task_get, port_url, agent_url, queue_add, and clear_queue.
See the MCP server overview for the full tool list and per-tool references for parameters and response formats.
Examples
Start the MCP server
claude mcp add.
Start with debug logging
~/.murmur/mcp.log. Useful for diagnosing tool call failures or unexpected responses.
Override the workspace
Errors
| Code | Meaning | What to do |
|---|---|---|
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur auth or check your murmur.local.yaml configuration. |
| config load failure | murmur.yaml is missing or invalid. | Ensure your repository has a valid .murmur/murmur.yaml. |
Related
- MCP server overview — how the MCP server fits into the Murmur architecture and the full list of exposed tools
- Agents — concept overview
murmur version— check client and server versions