MCP server

Ask your editor what broke. Mushi sends back the report, the plain-English read, and a fix brief — without leaving the window.

Model Context Protocol (MCP) is how your editor talks to Mushi tools — reports, fix briefs, and optional dispatch without leaving the chat.

Fastest path — one click. Open the Connect page to pick your client and install in one click, or try the read-only demo with no signup. Prefer the terminal? The one-liner below is just as quick.

One-liner setup (recommended)


npx mushi-mushi setup --ide cursor
# or: npx mushi-mushi setup --ide claude

This reads CLI config at ~/.config/mushi/config.json (written by mushi login; legacy ~/.mushirc auto-migrates on first load), detects the IDE config path, and writes the mcpServers block for you. Restart the IDE and ask the agent: “list mushi tools”.

Smithery (hosted MCP)

Install from the Smithery registry with Streamable HTTP at https://kensaur.us/mushi-mushi/hosted-mcp/. The server card at /.well-known/mcp/server-card.json lists every tool for directory scanners.

Run npx mushi-mushi project create on a brand-new machine to sign up, mint a project, and write .env.local + .cursor/mcp.json in one flow.

Manual setup: Cursor

Add to .cursor/mcp.json in your repo root:

.cursor/mcp.json


{
  "mcpServers": {
    "mushi": {
      "command": "npx",
      "args": ["-y", "@mushi-mushi/mcp@latest"],
      "env": {
        "MUSHI_API_ENDPOINT": "https://<your-ref>.supabase.co/functions/v1/api",
        "MUSHI_PROJECT_ID": "YOUR_PROJECT_ID",
        "MUSHI_API_KEY": "mushi_live_..."
      }
    }
  }
}

Mint a key on Projects → Generate API key or use Connect & Update → Add to Cursor. The RevealedKeyCard includes a ready-made .cursor/mcp.json snippet.

Manual setup: Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):


{
  "mcpServers": {
    "mushi": {
      "command": "npx",
      "args": ["-y", "@mushi-mushi/mcp@latest"],
      "env": {
        "MUSHI_API_ENDPOINT": "https://<your-ref>.supabase.co/functions/v1/api",
        "MUSHI_PROJECT_ID": "YOUR_PROJECT_ID",
        "MUSHI_API_KEY": "mushi_live_..."
      }
    }
  }
}

Hosted Streamable HTTP transport (no subprocess)

Skip the local subprocess — use the hosted MCP endpoint when you’re running OpenAI Agents SDK, ChatGPT Agent, CrewAI, or any remote orchestrator:

.cursor/mcp.json


{
  "mcpServers": {
    "mushi-hosted": {
      "url": "https://dxptnwrhwsqckaftyymj.supabase.co/functions/v1/mcp",
      "headers": {
        "X-Mushi-Api-Key": "mushi_live_…",
        "X-Mushi-Project-Id": "proj_…"
      }
    }
  }
}

Available tools

Tool	Purpose
`get_recent_reports`	Filter by status, severity, component
`get_report_detail`	Full detail incl. screenshot + classification
`get_fix_context`	One-shot fix brief — root cause + blast radius + repro
`search_reports`	Semantic + keyword search across reports
`dispatch_fix`	Start the Mushi fix agent for a report
`triage_next_steps`	”What should I fix next?” — 5-item plan from the dashboard
`query_knowledge_graph`	Ask “what other reports look like this?”
`run_nl_query`	Natural-language → SQL questions about your data

The MCP server speaks JSON-RPC 2.0 with tools/call semantics, and the agent surface is also discoverable via the A2A Agent Card at /.well-known/agent-card.

Cursor rules hook (optional)

After setup, run:


npx mushi-mushi setup --ide cursor --with-rules

This writes a .cursorrules file that tells Cursor to call get_fix_context before writing a fix and submit_fix_result after — closing the loop from inside the editor. Download the template: cursor.cursorrules

Smithery registry

Hosted Streamable HTTP endpoint: https://kensaur.us/mushi-mushi/hosted-mcp/

Install from the Smithery server page . Tool metadata is also published at /.well-known/mcp/server-card.json for directory scanners.

Troubleshooting

Not seeing what you expected?