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. To run only that registration step, run murmur setup --mcp. To add it manually:
On agent VMs, no setup is needed: the MCP server is auto-configured at boot.

​
Remote MCP URL

The setup above runs murmur mcp as a local process. To connect an MCP client directly without running that binary, use Murmur’s remote endpoint:
  • URL: https://api.murmur.dev/mcp
  • Auth: OAuth 2.1. Tools act on behalf of the signed-in user, scoped to the same tenants and permissions you have in the dashboard.
  • Transport: MCP Streamable HTTP.
The first time your client connects, Murmur sends you through a browser sign-in and consent screen; the client stores the token it receives and reuses it. Every call then acts as you, with your personal Murmur credentials. The remote endpoint does not accept header- or token-based auth: the URL is all your client needs, and the client drives the OAuth flow itself.

​
Claude Code

Claude Code doesn’t open a browser on its own. It flags the server as needing authentication. Complete the OAuth sign-in by running /mcp inside Claude Code, or claude mcp login murmur from your shell, then follow the browser prompt. Approve it once and the connection stays authenticated.

​
Other clients

Point any OAuth 2.1-capable MCP client at the URL:
The client discovers Murmur’s authorization server from the endpoint and runs the sign-in flow. No API key or header required.
The remote URL authenticates you over OAuth as yourself. For headless or service-identity access, such as a CI job or hosted platform with no browser, use a Service Profile API key with the local murmur mcp server. The remote endpoint does not support header- or key-based authentication.The remote endpoint’s tool set isn’t identical to the local server’s: it has no VM or local-disk context, so upload and port_url aren’t exposed. The tables below list the local murmur mcp tools.

​
Available tools

The tables below list the main tools the MCP server exposes:

​
Agent lifecycle

​
Dashboard folders

Personal folders that organize your dashboard sidebar. Every tool names a folder by its display name; spawn_profiles lists the names you have.

​
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.