Claude MCP Bridge — AI skill for Claude Code

claude-mcp-bridge

MCP server that lets **any** agent or MCP host (Cursor, Codex, Antigravity, another Claude Code, your own app) escalate to **Opus** via **Claude Code** running headless (`claude -p` / `claude --bg`).

Opus is **expensive but very capable** — this bridge is deliberately narrow: complex reasoning, architecture questions, adversarial review, and autonomous work. Cheap mechanical work (mapping a repo, scanning files) should stay on the host agent's lighter model.

Nested MCP delegation is **blocked**: Opus sessions spawned by this bridge cannot call claude-mcp-bridge (or any MCP) again.

Tools

Tool	Purpose	Model
ask	Read-only Q&A — architecture, explanation, planning (claudecode({ prompt: "..." }))	Opus (forced)
delegate	Full autonomous task — edit, shell, tests (max turns, synchronous)	Opus (forced)
fire	Fire-and-forget background task — returns session_id immediately	Opus (forced)
check	Compact progress report for a fire session	read-only (no model)
follow_up	Continue a prior session by session_id	Opus (forced)

Parallel background tasks

fire({ prompt: "Refactor the auth module to use JWT" })
→ returns session_id immediately

check({ session_id: "..." })
→ check progress anytime

Examples

// Ask Opus to explain architecture (read-only)
{ "prompt": "Explain the architecture of this project" }

// Delegate autonomous work (waits for completion)
{ "prompt": "Refactor auth to JWT and fix all tests" }

// Background refactor — poll while you keep working
{ "prompt": "Refactor the auth module to use JWT", "name": "JWT refactor" }
// → session_id: ...
{ "session_id": "..." }

Every tool accepts: `cwd` (project root), `effort` (`low` \| `medium` \| `high`, default `high`).

Requirements

• Node ≥ 18
• `claude` CLI v2.1.139+ installed and authenticated (claude once to log in).