Skip to main content
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, 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

​
Behavior

The server reads JSON-RPC requests from stdin and writes responses to stdout. It runs until the input stream closes or the process receives SIGINT 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 the claude/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 — including spawn, 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

The server begins reading JSON-RPC requests from stdin. In practice, Claude Code launches this process automatically once it has been registered with claude mcp add.

​
Start with debug logging

All JSON-RPC traffic is appended to ~/.murmur/mcp.log. Useful for diagnosing tool call failures or unexpected responses.

​
Override the workspace

​
Errors