Mushi Mushi

Name: Mushi Mushi
Author: kensaurus

by kensaurusversion 0.30.4i★ –iComputer or cloud

Registry nameio.github.kensaurus/mushi-mushi

Install

Overview

Description from the maker (original English)

The bug mediator for AI-built apps: plain-English diagnosis + a ready fix, in your editor.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: MUSHI_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: MUSHI_API_KEY, MUSHI_PROJECT_ID, MUSHI_API_ENDPOINT, MUSHI_FEATURES

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://kensaur.us/mushi-mushi/hosted-mcp/

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "mushi-mushi": {
      "command": "npx",
      "args": [
        "-y",
        "@mushi-mushi/mcp"
      ],
      "env": {
        "MUSHI_API_KEY": "your-value",
        "MUSHI_PROJECT_ID": "your-value",
        "MUSHI_API_ENDPOINT": "your-value",
        "MUSHI_FEATURES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http mushi-mushi https://kensaur.us/mushi-mushi/hosted-mcp/

Or run it on your computer

claude mcp add mushi-mushi --env MUSHI_API_KEY=your-value --env MUSHI_PROJECT_ID=your-value --env MUSHI_API_ENDPOINT=your-value --env MUSHI_FEATURES=your-value -- npx -y @mushi-mushi/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mushi-mushi": {
      "url": "https://kensaur.us/mushi-mushi/hosted-mcp/"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mushi-mushi": {
      "command": "npx",
      "args": [
        "-y",
        "@mushi-mushi/mcp"
      ],
      "env": {
        "MUSHI_API_KEY": "your-value",
        "MUSHI_PROJECT_ID": "your-value",
        "MUSHI_API_ENDPOINT": "your-value",
        "MUSHI_FEATURES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "mushi-mushi": {
      "type": "http",
      "url": "https://kensaur.us/mushi-mushi/hosted-mcp/"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "mushi-mushi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mushi-mushi/mcp"
      ],
      "env": {
        "MUSHI_API_KEY": "your-value",
        "MUSHI_PROJECT_ID": "your-value",
        "MUSHI_API_ENDPOINT": "your-value",
        "MUSHI_FEATURES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://kensaur.us/mushi-mushi/hosted-mcp/

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

MUSHI_API_KEY secret required env
Project ingest/admin API key minted in the Mushi console (Settings → API Keys). Scope mcp:read for triage, mcp:write to dispatch fixes.
MUSHI_PROJECT_ID env
Project UUID the key belongs to. Optional for single-project account keys.
MUSHI_API_ENDPOINT env
Override the API base URL (self-hosted deployments). Defaults to the hosted Mushi Cloud endpoint.
MUSHI_FEATURES env
Comma-separated feature groups to expose (triage,fixes,inventory,setup,docs). Defaults to the lean catalog; use 'all' for the full tool set.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kensaurus, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 589 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18323 servers in this category
Published to the registry more recently than 97% of the other 18323 servers in this category
Basic checks equal to or better than 100% of the other 18323 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Mushi Mushi safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MUSHI_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.30.4) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Date Math

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Date Math

by JowenDelaPena

Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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" } } } }

Variable	Where to find it
`MUSHI_API_KEY`	Console → Connect or MCP: mint an `mcp:read` or `mcp:write` key. Not the SDK key from Setup → Verify, and not an AI key from Settings
`MUSHI_PROJECT_ID`	Console → Projects → the UUID under your project's name
`MUSHI_API_ENDPOINT`	Optional. Only for self-hosting, e.g. `http://localhost:54321/functions/v1/api`
`MUSHI_FEATURES`	Optional. Tool groups to expose (see below)

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

Start here	What it does
`triage_next_steps`	What needs attention right now, from the live queue
`get_fix_context`	One brief for a report: root cause, repro, the smallest set of files
`triage_issue`	Everything about one report: evidence, similar bugs, blast radius, logs, next actions
`dispatch_fix` / `merge_fix`	Have an agent open a draft PR, then merge it and close the report
`diagnose_setup`	Explains a broken install and the one next step
`search_mushi_docs`	Answers setup and API questions from the docs

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

Scope	Can do	Give it to
`report:write`	Send reports only. No admin access	Your app's SDK. Never an MCP client
`mcp:read`	Every read tool and resource	Most agent loops
`mcp:write`	Reads plus `dispatch_fix`, `merge_fix`, `transition_status` and other changes	Agents that should act on bugs

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

Import	Exports
`@mushi-mushi/mcp/server`	`createMushiServer()` for a custom host
`@mushi-mushi/mcp/catalog`	`TOOL_CATALOG`, scopes and tool specs
`@mushi-mushi/mcp/feature-groups`	Feature-group filtering
`@mushi-mushi/mcp/clients`	The supported editors and how each one installs
`@mushi-mushi/mcp/branding`	Icons and server metadata

Learn more

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

License

MIT

Mushi Mushi

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Date Math

README from the maker

@mushi-mushi/mcp

Quick start

Manual setup (any MCP client)

What your editor gets

Keys and safety

Troubleshooting

Programmatic use

Learn more

License