Install mumo in Cursor.

Generate your API key

Sign in, create a mumo API key, and copy the value that starts with mmo_live_. You'll set it as an environment variable in the next step.

Set MUMO_API_KEY for Cursor

The plugin's MCP config expects ${env:MUMO_API_KEY}. On macOS, set it where GUI apps inherit it — from Terminal:

launchctl setenv MUMO_API_KEY mmo_live_YOUR_KEY_HERE

Then fully restart Cursor with Cmd+Q and reopen it (Cmd+R reload is often not enough for env propagation).

Optional: add export MUMO_API_KEY=mmo_live_YOUR_KEY_HERE to ~/.zshrcso Terminal-launched tooling sees the same key — this alone does not guarantee Cursor opened from Dock/Spotlight will see it (that's why launchctl setenv is listed first).

In Cursor Tools & MCP, the server named mumo should go green once this path works. If it stays red even though launchctl getenv MUMO_API_KEYsucceeds in Terminal, use step 04 — that's a known Cursor variance with plugin-contributed MCP, not your key.

Install the mumo plugin

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 new plugin. The MCP server, skill, subagent, and rule all activate together.

If the plugin MCP stays red

Sometimes Cursor shows the contributed server mumoin Tools & MCP as errored while the API key works everywhere else (launchctl getenv MUMO_API_KEY succeeds, curl to mumo.chat/api/mcp succeeds). Community reports indicate ${env:…}interpolation for remote MCP doesn't always resolve the same path for Cursor plugins vs user configs — e.g. this forum thread.

Reliable fallback: merge an entry into your user-level MCP file ~/.cursor/mcp.json (Cursor merges that with project .cursor/mcp.json when present). Use any server label you want; mumo skill and rule bind to tool names (create_deliberation, …), not the label.

{
  "mcpServers": {
    "mumo-manual": {
      "url": "https://mumo.chat/api/mcp",
      "headers": {
        "Authorization": "Bearer mmo_live_YOUR_KEY_HERE"
      }
    }
  }
}

If you'd rather not embed the literal key, Cursor's resolver often accepts "Authorization": "Bearer ${env:MUMO_API_KEY}" in this file instead — combine with step 02 as usual.

In Tools & MCP, turn off the broken mumoconnector so the agent doesn't latch onto the failing one. Leave your merged server enabled; skill and routing still apply. Don't commit plaintext keys inside a tracked repo (mcp.json belongs in your home dotfiles or secrets storage, not the project remote).

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.