@ziggs-ai/ziggs-mcp 0.1.8 → 0.1.10

package/README.md

@@ -154,9 +154,9 @@ Startup validates the key shape, expiry (JWT `exp`), and agent resolution — er
 
 ### 4. CLI smoke scripts
 
-```bash
-cd agentplus
+From the **repository root** ([github.com/ZiggsAI/agentplus](https://github.com/ZiggsAI/agentplus)):
 
+```bash
 # ZIG-222
 ZIGGS_OPERATOR_KEY=... ZIGGS_AGENT_ID=cursor-delegate \
   node scripts/smoke-ziggs-mcp.mjs
@@ -187,7 +187,7 @@ ZIGGS_SMOKE_CHAT_ID=... \
 
 | Tool | Maps to |
 |------|---------|
-| `ziggs_inbox` | `GET /agent-api/v1/inbox` + `POST .../ack` (ZIG-434) |
+| `ziggs_inbox` | `GET /inbox` + `POST /inbox/ack` (ZIG-434, ZIG-491) |
 | `ziggs_discover_context` | `GET /context/discovery` |
 | `ziggs_read_context` | `GET /context/read/:type` |
 | `ziggs_record_artifact` | `POST /artifacts` |
@@ -213,7 +213,6 @@ ZIGGS_SMOKE_CHAT_ID=... \
 ## Develop
 
 ```bash
-cd agentplus
 npm install
 npm run build -w @ziggs-ai/ziggs-mcp
 npm test -w @ziggs-ai/ziggs-mcp

package/examples/claude-ai-oauth.md

@@ -15,7 +15,7 @@ Manual smoke runbook for the **real claude.ai connector UI**. Automated coverage
 Automated probe (same guarantee, no claude.ai UI):
 
 ```bash
-cd agentplus
+# from github.com/ZiggsAI/agentplus clone root
 node scripts/smoke-ziggs-mcp-oauth-z474-consent-probe.mjs --auto
 ```
 
@@ -94,7 +94,7 @@ If you are already logged in, you still see this screen (ZIG-474). You are **not
 Full API path smoke (no claude.ai UI):
 
 ```bash
-cd agentplus
+# from github.com/ZiggsAI/agentplus clone root
 node scripts/smoke-ziggs-mcp-oauth-z468-e2e.mjs --auto
 node scripts/smoke-ziggs-mcp-oauth-z474-consent-probe.mjs --auto
 ```

package/examples/claude-code-remote-mcp.json

@@ -1,6 +1,7 @@
 {
   "mcpServers": {
     "ziggs": {
+      "type": "http",
       "url": "https://mcp.ziggsai.com/mcp"
     }
   }

package/examples/claude-code-remote-oauth.md

@@ -5,9 +5,12 @@ Verify the **fresh Claude Code** journey: empty repo, `.mcp.json` only (no opera
 Automated prerequisites + Path A parity (no UI):
 
 ```bash
-cd agentplus
+# from github.com/ZiggsAI/agentplus clone root
 node scripts/smoke-zig-500-v4-path.mjs --discovery-only
 node scripts/smoke-zig-500-v4-path.mjs --auto
+node scripts/smoke-zig-500-v4-claude-code.mjs   # Claude Code CLI parity
+# or:
+./scripts/run-zig-500-v4-claude-code.sh
 ```
 
 ---
@@ -19,11 +22,12 @@ node scripts/smoke-zig-500-v4-path.mjs --auto
 | ZIG-496 discovery (well-known, 401 docs) | `--discovery-only` | Client uses same URLs |
 | OAuth → Bearer → full tool surface | `--auto` or smoke creds | Connect in IDE |
 | No stub-only tools | fails if only `authenticate` / `complete_authentication` | Tool picker shows `ziggs_*` |
+| Runtime tools work | `ziggs_connection_status` + `ziggs_inbox` | Same smoke in IDE |
 | Restart not required | N/A | Tools visible right after OAuth |
 
-**Path A (pass):** Native MCP OAuth — client discovers metadata, gets Bearer, `tools/list` returns ≥12 `ziggs_*` tools.
+**Pass:** Native MCP OAuth — client discovers metadata, gets Bearer, `tools/list` returns ≥12 `ziggs_*` tools, and inbox/connection_status succeed.
 
-**Path B (fail → epic children 501–502):** OAuth succeeds but only stub auth tools appear — needs unauth MCP + `tools/list_changed` design in backend.
+**Fail:** OAuth OK but tools empty, stub-only list, or inbox 404 → comment on [ZIG-500](https://linear.app/ziggsai/issue/ZIG-500) with tool list + smoke output.
 
 ---
 
@@ -37,6 +41,7 @@ Copy [`claude-code-remote-mcp.json`](claude-code-remote-mcp.json):
 {
   "mcpServers": {
     "ziggs": {
+      "type": "http",
       "url": "https://mcp.ziggsai.com/mcp"
     }
   }
@@ -52,19 +57,18 @@ Use a **throwaway directory** (no existing Ziggs plugin or stdio MCP).
 ### 3. Connect / authorize
 
 1. Claude Code should prompt for MCP OAuth (or open MCP settings).
-2. Browser → Ziggs consent (`/app/oauth/mcp-consent`) → **Allow**.
+2. Browser → Ziggs consent (`/app/oauth/mcp-consent`) — pick **org** if you have teams → **Allow**.
 3. Return to Claude Code — check tool list.
 
 ### 4. Smoke tools (no restart)
 
 Ask Claude to call in order:
 
-1. `ziggs_list_chats` or `ziggs_inbox`
-2. `ziggs_send_message` (chat you belong to)
+1. `ziggs_connection_status` — confirm agent + org binding
+2. `ziggs_inbox` or `ziggs_list_chats`
+3. `ziggs_send_message` (chat you belong to)
 
-**Pass:** both succeed; tool picker shows many `ziggs_*` tools (not just 2 auth stubs).
-
-**Fail:** only `authenticate` / `complete_authentication`; or OAuth OK but tools empty until restart → comment on [ZIG-500](https://linear.app/ziggsai/issue/ZIG-500) with Path B.
+**Pass:** all succeed; tool picker shows many `ziggs_*` tools (not just 2 auth stubs).
 
 ---
 
@@ -92,9 +96,9 @@ For dev or when OAuth is blocked, use [claude-code.md](claude-code.md) Option B
 | Symptom | Check |
 |---------|--------|
 | OAuth loop / 401 on tools | Re-run `smoke-zig-500-v4-path.mjs --auto`; revoke MCP in Agents dashboard → reconnect |
-| Only 2 stub tools | Path B — epic needs 501/502; paste tool list in Linear |
-| `app.ziggsai.com` in 401 `error` text | ZIG-496 fixed `docs` field; `error` string comes from pinned `@ziggs-ai/ziggs-mcp` npm — bump backend dep after publish |
-| Tools after restart only | ZIG-502 `tools/list_changed` candidate |
+| Only 2 stub tools | Should not happen on current prod (Bearer-only `/mcp`); paste tool list in ZIG-500 |
+| `ziggs_inbox` 404 | Backend must pin `@ziggs-ai/ziggs-mcp@0.1.9+` (ZIG-491 `/inbox` path); npm 0.1.10+ fixes Claude Code `.mcp.json` example (`type: http`) |
+| Wrong org | Reconnect; pick org on consent screen (ZIG-504) |
 
 ---
 
@@ -106,9 +110,10 @@ Date:
 Claude Code version:
 Repo: empty + .mcp.json only (Y/N)
 Automated: smoke-zig-500-v4-path.mjs --discovery-only → pass/fail
-Automated: smoke-zig-500-v4-path.mjs --auto → Path A/B, N tools
+Automated: smoke-zig-500-v4-path.mjs --auto → Path A, N tools, inbox pass/fail
 Manual OAuth connect: pass/fail
 Tool count after OAuth (no restart): __
-ziggs_inbox or ziggs_list_chats: pass/fail
+ziggs_connection_status: pass/fail
+ziggs_inbox: pass/fail
 Notes:
 ```

package/examples/claude-code.md

@@ -58,7 +58,7 @@ Ask Claude to call tools in order:
 Paste the session transcript in the PR when verifying ZIG-430, or run:
 
 ```bash
-cd agentplus
+# from github.com/ZiggsAI/agentplus clone root
 ZIGGS_OPERATOR_KEY=<agent-scoped> node scripts/smoke-ziggs-mcp-z430-e2e.mjs
 ```
 

package/examples/cursor-remote-oauth.md

@@ -80,7 +80,7 @@ Points `authorization_servers` → `https://api.ziggsai.com` and lists MCP scope
 Automated parity probe:
 
 ```bash
-cd agentplus
+# from github.com/ZiggsAI/agentplus clone root
 node scripts/probe-cursor-oauth-parity.mjs
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "MCP server for Claude Code, Cursor, and other MCP hosts — act as your Ziggs delegate agent",
   "type": "module",
   "bin": {
@@ -34,14 +34,20 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@ziggs-ai/api-client": "^0.1.9",
+    "@ziggs-ai/api-client": "^0.1.11",
     "dotenv": "^16.6.1",
     "zod": "^3.24.2"
   },
   "engines": {
     "node": ">=20"
   },
-  "keywords": ["ziggs", "mcp", "claude", "cursor", "model-context-protocol"],
+  "keywords": [
+    "ziggs",
+    "mcp",
+    "claude",
+    "cursor",
+    "model-context-protocol"
+  ],
   "license": "MIT",
   "files": [
     "dist",