← MCP Install · Cursor

Install mumo in Cursor.

mumo ships as a Cursor plugin with an auto-triggering skill, a moderator subagent, and a routing rule. Cursor doesn't expose a native keychain for plugin secrets, so the API key flows through an environment variable.

01

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.

02

Set MUMO_API_KEY for Cursor

Cursor reads ${env:MUMO_API_KEY} when it starts. On macOS, set it for your apps from Terminal with:

launchctl setenv MUMO_API_KEY mmo_live_YOUR_KEY_HERE

Then fully restart Cursor with Cmd+Q and reopen it.

Optional: also add export MUMO_API_KEY=mmo_live_YOUR_KEY_HERE to ~/.zshrc if you want terminal sessions to have the key too.

03

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.

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