← MCP Install · Cursor

Install mumo in Cursor.

Two pieces: a one-click install link that writes the mumo server into your Cursor config, and a plugin that adds the auto-triggering skill, moderator subagent, and routing rule. No environment variables, no terminal, works the same on every OS.

01

Generate your API key

Sign in, create a mumo API key, and copy the value that starts with mmo_live_. You'll paste it in the next step.

02

Add mumo to Cursor

Paste your key and click. Cursor opens an Install MCP Server dialog pre-filled with the mumo server — review it and click Install. The server lands in your user-level MCP config: survives restarts and reboots, identical on macOS, Linux, and Windows.

Built in your browser — the key is never sent to us or stored on this page.

Prefer not to click a protocol link? Merge the same entry into ~/.cursor/mcp.json by hand — identical result:

{
  "mcpServers": {
    "mumo": {
      "url": "https://mumo.chat/api/mcp",
      "headers": {
        "Authorization": "Bearer mmo_live_YOUR_KEY_HERE"
      }
    }
  }
}
Cursor's Install MCP Server dialog, pre-filled with the mumo server URL and Authorization header

Either way, confirm in Cursor under Tools & MCP: the server named mumo shows green with 8 tools enabled.

Cursor's Installed MCP Servers panel showing mumo green with 8 tools enabled

Keys are revocable any time from your dashboard; keep ~/.cursor/mcp.json in your home dotfiles, not a tracked repo.

Upgrading from the old mumo plugin? Uninstall it first (Cursor Settings → Plugins → mumo → Uninstall). Pre-0.6.0 versions bundled their own mumo server, which blocks this install silently — the dialog never appears. Reinstall the plugin in step 03 afterward; current versions ship no server.

03

Install the mumo plugin

The plugin adds the behavior layer — an auto-triggering skill, a moderator subagent, and a routing rule. Sideload from GitHub while the Cursor marketplace listing rolls out:

git clone https://github.com/mumo-chat/mumo-cursor ~/.cursor/plugins/local/mumo

Restart Cursor (or reload the window) so it picks up the plugin. It contributes no server of its own — the skill and rule bind to the tool names (create_deliberation, …) from the server you added in step 02.

04

Run your first deliberation

Cursor's rule system treats plugin rules and skills as soft priors. Name mumo explicitly the first time so the agent reaches for the panel instead of answering directly.

Ask mumo to compare Postgres and MongoDB for our event store.
Include the constraints from this repo and tell me where the models disagree.

Reliable invocations: “Ask mumo about…”, “Run this by a mumo panel”, “Get me a second opinion from mumo on…”. Vague phrasings like “ask a panel” may resolve to a generic response — the word mumo is what makes the routing stick.

Plugin source: github.com/mumo-chat/mumo-cursor · MCP tool reference · Other clients