Setup
If you ranmurmur setup and accepted the MCP prompt, the server is already configured. Otherwise, add it manually:
Available tools
The MCP server exposes 17 tools:Agent lifecycle
| Tool | Purpose |
|---|---|
spawn | Create a new agent |
spawn_profiles | List the identities you can spawn an agent as |
status | Query an agent’s current state |
ls | List agents |
kill | Cancel an agent and its subtree |
interrupt | Interrupt an agent’s current turn |
wait | Block until an agent reaches a target phase |
queue_add | Send a follow-up message to a running agent |
clear_queue | Discard all queued follow-ups |
Task management
| Tool | Purpose |
|---|---|
task_create | Add an item to an agent’s checklist |
task_update | Update task status, description, or dependencies |
task_list | List all tasks in an agent’s checklist |
task_get | Retrieve a single task by ID |
Utilities
Slug targeting
Tools that target an agent accept aslug parameter. Slugs follow two forms:
Relative — a bare name like fix-bug resolves relative to the calling agent. On a VM, it targets a child. On a laptop, it targets a root agent.
Absolute — a path starting with / overrides the caller’s context: /w/workspace/u/account/slug.
When slug is omitted, most tools target the calling agent itself.
Channel events
On agent VMs, the MCP server pushes real-time events via theclaude/channel capability. Events arrive as <channel> tags — PR comments, CI results, child lifecycle changes, and file-changed notifications. Agents react to these without polling.