Mushi Mushi

@mushi-mushi/mcp

Your AI wrote it. Mushi Mushi tells you why it broke.

The Model Context Protocol server for Mushi Mushi. It lets Cursor, Claude Code, VS Code or any MCP client read your app's bug reports, get a plain-English diagnosis with a fix to start from, and dispatch or merge fixes. Your editor's own model does the work, so reading reports and fixing them in your editor needs no second AI key. Handing a fix to an agent with dispatch_fix is different: it runs the app's fix agent, which on hosted Mushi Mushi is the built-in fixer by default (no key of your own needed); Cursor's agents need your Cursor key, or run on your computer with the Mushi Mushi worker.

Docs: MCP guide · tool reference

flowchart LR

A["Bug reports in Mushi Mushi"] --> B["This MCP server"] --> C["Your editor 'what's broken in prod?'"] --> D["Fix: you, or a draft PR from an agent"]

Quick start

npx mushi-mushi setup --ide cursor   # or: claude, continue, zed

Restart the editor and ask *"what's broken in prod?"*. For Cursor and Claude, setup writes the hosted server entry: the editor opens a browser sign-in on first use, and no API key is stored on disk. Pass --stdio for a local server, or --with-rules to also write the lesson-library rules file. You can also use the one-click Add to Cursor button on the connect page.

Manual setup (any MCP client)

{

"mcpServers": { "mushi-mushi": { "command": "npx", "args": ["-y", "@mushi-mushi/mcp@0.30.4"], "env": { "MUSHI_API_KEY": "mushi_xxxxxxxxxxxxxxxxxxxx", "MUSHI_PROJECT_ID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" } } } }

Claude Desktop does not expand ${VAR} references in this file; Cursor and VS Code expand ${env:MUSHI_API_KEY} and Claude Code expands ${MUSHI_API_KEY}. Keep the key out of any mcp.json you commit.

What your editor gets

The full catalog has 130 tools, plus 8 resources (project://dashboard, project://stats, …) and 4 prompts (summarize_report_for_fix, triage_next_steps, …). Every tool carries read-only and destructive hints, so your editor can ask before it changes anything. Full list: MCP tool reference.

Tool groups. New installs get a lean default: triage, fixes, inventory, setup, docs. Turn on more with MUSHI_FEATURES=triage,qa,codebase (stdio) or ?features=… on the hosted URL, or everything with all. Groups: qa, skills, codebase, rewards, admin, audit, usage. For a chat tool such as Lovable, or an editor that caps how many tools it loads, vibe gives about a dozen tools for the core loop. Add ?read_only=1 to the hosted URL to hide every write tool.

Keys and safety

A key without the needed scope gets a clear INSUFFICIENT_SCOPE error, never a silent failure. Your SDK key ships in your app's bundle, so it must never carry mcp:write; the console mints MCP keys separately. Never use a Supabase service-role key. If a laptop is lost, rotate the key in the console.

Troubleshooting

• No tools showing? Check the MCP panel for a green dot, then fully restart the editor after any config change.
• Keep one config. Put the Mushi Mushi entry in your global ~/.cursor/mcp.json only; a second copy in a project file can cause connection storms.
• Windows paths in JSON need forward slashes (C:/Users/...) or escaped backslashes.
• Still stuck? Ask your editor to run diagnose_setup, or run mushi doctor --mcp.

Programmatic use

Learn more

MCP guide · MCP quickstart · The incident loop · How agent fixes work · Sample diagnosis

License

MIT