Skip to main content
The Murmur MCP server exposes agent operations as tools over the Model Context Protocol. Claude Code discovers these tools automatically and invokes them alongside its built-in tools.

​
Setup

If you ran murmur setup and accepted the MCP prompt, the server is already configured. Otherwise, add it manually:
On agent VMs, no setup is needed — the MCP server is auto-configured at boot.

​
Available tools

The MCP server exposes 17 tools:

​
Agent lifecycle

​
Task management

​
Utilities

​
Slug targeting

Tools that target an agent accept a slug 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}/{owner_provider}/{account}/{slug}, where {owner_provider} is a provider string like github_oauth or service_profile — e.g. /w/backend/github_oauth/alice/fix-auth. When slug is omitted, most tools target the calling agent itself.

​
Channel events

On agent VMs, the MCP server pushes real-time events via the claude/channel capability. Events arrive as <channel> tags — PR comments, CI results, child lifecycle changes, and file-changed notifications. Agents react to these without polling.