Mushi Mushi MCP Server

Bug translation for vibe coders: plain-English diagnosis + paste-ready fix in your AI coding agent

Remote serverstreamable-httpGo

What is the Mushi Mushi MCP server?

Bug translation for vibe coders: plain-English diagnosis + paste-ready fix in your AI coding agent. The mushi mushi mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

Plain-English diagnosis + a paste-ready fix, right inside Cursor and Claude Code. No log-reading. No second LLM API key for MCP.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

  • Catches — Thrown errors and silent UX bugs (dead clicks, slow screens, layout breaks)
  • Output — Plain-English root cause + paste-ready fix, in your editor
  • Auto-fix — Optional: sandbox agent opens a draft PR
  • Setup — One command, no account required to try
  • Area — Working
  • Classification — Haiku fast-filter, Sonnet deep + vision air-gap closed, structured outputs, prompt-cached prompts, pg_cron self-healing, **Stage 2 streaming via
  • Sandbox — Provider abstraction; local-noop (tests) + e2b / modal / cloudflare (prod). Production refuses local-noop unless MUSHI_ALLOW_LOCAL_SANDBOX=1
  • Verify — Playwright screenshot diff + step interpreter (navigate / click / type / press / select / assertText / waitFor / observe)
  • Enterprise — Plugin marketplace + HMAC, audit ingest, region pinning, retention CRUD, Stripe metering, SAML SSO via Supabase Auth Admin API, **OIDC SSO
  • Surface — License
  • App — What it does

Configuration

You will need 4 environment variables: VITE_MUSHI_PROJECT_ID, VITE_MUSHI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mushi Mushi.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mushi mushi mcp server does with a few real requests.

When to reach for it

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mushi Mushi's toolset — Catches, Output, Auto-fix and 8 more — is a fair guide to whether it matches your workflow. It is maintained by kensaurus; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
CatchesThrown errors **and** silent UX bugs (dead clicks, slow screens, layout breaks)
OutputPlain-English root cause + paste-ready fix, in your editor
Auto-fixOptional: sandbox agent opens a draft PR
SetupOne command, no account required to try
AreaWorking
ClassificationHaiku fast-filter, Sonnet deep + **vision air-gap closed**, structured outputs, prompt-cached prompts, pg_cron self-healing, **Stage 2 streaming via streamObject with progressive reports.stage2_partial UI updates and Ope
SandboxProvider abstraction; local-noop (tests) + e2b / modal / cloudflare (prod). Production refuses local-noop unless MUSHI_ALLOW_LOCAL_SANDBOX=1.
VerifyPlaywright screenshot diff + step interpreter (navigate / click / type / press / select / assertText / waitFor / observe)
EnterprisePlugin marketplace + HMAC, audit ingest, region pinning, retention CRUD, Stripe metering, **SAML SSO via Supabase Auth Admin API**, **OIDC SSO self-service** — see the [commercial boundary](#license--branding) below for
SurfaceLicense
AppWhat it does

How to install the Mushi Mushi MCP server

{
  "mcpServers": {
    "mushi-mushi": {
      "command": "npx",
      "args": ["-y", "mushi-mushi"],
      "env": {
        "VITE_MUSHI_PROJECT_ID": "your-value",
        "VITE_MUSHI_API_KEY": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
VITE_MUSHI_PROJECT_IDConfiguration value read at startup.Optional
VITE_MUSHI_API_KEYCredential the server authenticates with.Yes
ANTHROPIC_API_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Mushi Mushi to Catches.
  • Use Mushi Mushi to Output.
  • Use Mushi Mushi to Auto-fix.

Frequently asked questions

It connects Mushi Mushi to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (Catches, Output, Auto-fix, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mushi Mushi directly.