@mushi-mushi/mcp 0.5.0 → 0.6.0

package/README.md

@@ -1,6 +1,8 @@
 # @mushi-mushi/mcp
 
-[Model Context Protocol](https://spec.modelcontextprotocol.io/) server that exposes Mushi Mushi reports, fixes, and project state to coding agents (Claude Code, Cursor, Codex, Continue, Cline, Zed, Windsurf, and any other MCP-compatible client).
+[Model Context Protocol](https://spec.modelcontextprotocol.io/) server that wires Mushi Mushi's closed-loop bug intelligence into your AI coding agent — so Cursor, Claude Code, Copilot, and any other MCP-compatible client can read classified reports, query the lesson library, and dispatch AI-generated fixes directly from the editor.
+
+**The evolutionary angle:** the lesson library (`lessons.query` tool) is the agent's institutional memory. Every bug cluster your team has ever named is available to the agent before it touches a single line of code — so it doesn't repeat the same class of mistake the last agent made. That's the "cumulative selection" loop the [main README](https://www.npmjs.com/package/mushi-mushi) describes, delivered to your IDE.
 
 > **What this is, and what it isn't**
 >
@@ -21,9 +23,9 @@ Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
       "command": "npx",
       "args": ["-y", "@mushi-mushi/mcp@latest"],
       "env": {
-        "MUSHI_API_KEY": "key_xxx",
-        "MUSHI_PROJECT_ID": "proj_xxx",
-        "MUSHI_API_ENDPOINT": "https://api.mushimushi.dev"
+        "MUSHI_API_KEY": "mushi_xxxxxxxxxxxxxxxxxxxx",
+        "MUSHI_PROJECT_ID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+        "MUSHI_API_ENDPOINT": "https://<your-ref>.supabase.co/functions/v1/api"
       }
     }
   }
@@ -32,6 +34,13 @@ Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
 
 Restart Claude Desktop. You should see a hammer icon in the chat input — click it to see the Mushi Mushi tools.
 
+> **Where do I find these values?**
+> - **`MUSHI_API_KEY`**: [Admin console](https://kensaur.us/mushi-mushi/settings) → **Settings → API Keys**
+> - **`MUSHI_PROJECT_ID`**: [Admin console](https://kensaur.us/mushi-mushi/projects) → click your project → copy the UUID below the project name (e.g. `542b34e0-019e-41fe-b900-7b637717bb86`)
+> - **`MUSHI_API_ENDPOINT`**: [Admin console](https://kensaur.us/mushi-mushi/settings) → **Settings → API Keys** — shown alongside your key
+>
+> Or visit **Admin → MCP** in the console for a one-click pre-filled config snippet.
+
 ### 2. With Cursor
 
 In Cursor settings, open **MCP** → **Add new MCP server** and paste:
@@ -40,12 +49,22 @@ In Cursor settings, open **MCP** → **Add new MCP server** and paste:
 npx -y @mushi-mushi/mcp@latest
 ```
 
-Set the same three env vars (`MUSHI_API_KEY`, `MUSHI_PROJECT_ID`, optional `MUSHI_API_ENDPOINT`).
+Then set the same three environment variables:
+
+| Variable | Where to find it |
+|---|---|
+| `MUSHI_API_KEY` | Admin console → Settings → API Keys |
+| `MUSHI_PROJECT_ID` | Admin console → Projects → click project → UUID below the name |
+| `MUSHI_API_ENDPOINT` | Admin console → Settings → API Keys (shown alongside your key) |
+
+Without `MUSHI_PROJECT_ID` the server starts but scoped tools return an empty result with a message pointing you here.
 
 ### 3. From the command line
 
 ```bash
-MUSHI_API_KEY=key_xxx MUSHI_PROJECT_ID=proj_xxx npx -y @mushi-mushi/mcp@latest
+MUSHI_API_KEY=mushi_xxxxxxxxxxxxxxxxxxxx \
+MUSHI_PROJECT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \
+npx -y @mushi-mushi/mcp@latest
 ```
 
 The server speaks stdio MCP transport by default — your client launches it as a subprocess.
@@ -59,10 +78,10 @@ The Mushi backend now exposes the same tool catalog over the **Streamable HTTP**
 {
   "mcpServers": {
     "mushi-mushi-hosted": {
-      "url": "https://api.mushimushi.dev/functions/v1/mcp",
+      "url": "https://<your-ref>.supabase.co/functions/v1/mcp",
       "headers": {
-        "X-Mushi-Api-Key": "mushi_live_…",
-        "X-Mushi-Project-Id": "proj_…"
+        "X-Mushi-Api-Key": "mushi_xxxxxxxxxxxxxxxxxxxx",
+        "X-Mushi-Project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
       }
     }
   }

package/dist/index.js

@@ -913,7 +913,7 @@ async function main() {
   }
   if (!PROJECT_ID) {
     console.error(
-      "[mushi-mcp] MUSHI_PROJECT_ID is not set.\n\nTools that scope to a project (get_recent_reports, get_report_detail,\nsearch_reports, etc.) will require you to pass projectId explicitly on\nevery call. To set it once and never pass it again:\n\n  1. Open the Mushi admin console \u2192 Projects\n     (https://your-admin-url/projects)\n  2. Find your project \u2014 the UUID chip below the name is the value to use.\n  3. Copy it and set:\n       MUSHI_PROJECT_ID=<paste-uuid-here>\n\nYou can also visit Admin \u2192 MCP for a pre-filled .env.local snippet."
+      "[mushi-mcp] MUSHI_PROJECT_ID is not set.\n\nTools that scope to a project (get_recent_reports, get_report_detail,\nsearch_reports, etc.) will require you to pass projectId explicitly on\nevery call. To set it once and never pass it again:\n\n  1. Open the Mushi admin console \u2192 Projects\n     https://kensaur.us/mushi-mushi/projects\n  2. Click your project \u2014 copy the UUID below the project name.\n  3. Add it to your MCP env config:\n       MUSHI_PROJECT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\n\nOr visit Admin \u2192 MCP for a pre-filled config snippet with your actual UUID."
     );
   }
   log.info("Starting Mushi MCP server", { version: VERSION, endpoint: API_ENDPOINT || "(unset)", hasProjectId: !!PROJECT_ID });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mushi-mushi/mcp",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "license": "MIT",
   "description": "MCP server exposing Mushi Mushi reports to coding agents",
   "type": "module",
@@ -26,7 +26,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.4.2",
-    "@mushi-mushi/core": "^1.1.0"
+    "@mushi-mushi/core": "^1.2.0"
   },
   "devDependencies": {
     "@types/node": "^22.19.17",