What can you do with this server?

This server bridges any MCP host to Claude Opus running headlessly, enabling powerful autonomous AI delegation. It offers the following tools: * ask — Pose read-only questions to Opus for architecture, planning, or explanations. * delegate — Hand off a complete autonomous task (file edits, shell commands, tests) to Opus, which runs its own agentic loop until completion. * fire — Start a background autonomous task and return immediately with a session_id for later progress checks. * check — Poll the status and progress of a background fire task by session_id. * follow_up — Continue a prior session by session_id without resending context, since it lives on Claude's side. * adversarial_review — Get a critical, read-only review of code, plans, or diffs — hunting for bugs, edge cases, security issues, and race conditions. Useful as a pre-merge gate. * web_lookup — Delegate a web/documentation lookup to Opus (with live web access) to find library docs, API references, error explanations, or current package versions. All tools support cwd (project root) and effort (low/medium/high) parameters, and most support model selection (defaulting to Opus). Delegated tasks also support permission controls (e.g., acceptEdits, bypassPermissions).

How do I use claude-mcp-bridge?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@claude-mcp-bridge analyze the src directory for bugs" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

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).

Related MCP server: agent-network

Requirements

Node ≥ 18
claude CLI v2.1.139+ installed and authenticated (claude once to log in). Background tasks (fire / check) require claude --bg and claude agents --json.

Install

git clone https://github.com/JaimeJunr/claude-mcp-bridge.git
cd claude-mcp-bridge
npm install
npm run build

Register in an MCP host

Claude Code:

claude mcp add claude-bridge -s user -- node /abs/path/to/claude-mcp-bridge/dist/index.js

Cursor / Codex / any host — add to its mcp.json:

{
  "mcpServers": {
    "claude-bridge": {
      "command": "node",
      "args": ["/abs/path/to/claude-mcp-bridge/dist/index.js"]
    }
  }
}

Configuration (env)

Var	Default	Meaning
`CLAUDE_BIN`	`claude`	Path to the `claude` binary.
`CLAUDE_BRIDGE_MODEL`	`opus`	Model alias — always Opus in this bridge.
`CLAUDE_BRIDGE_EFFORT`	`high`	Default reasoning effort.
`CLAUDE_BRIDGE_MAX_TURNS`	`20`	Max agentic turns for `delegate` / `fire`.
`CLAUDE_BRIDGE_PERMISSION`	`acceptEdits`	Permission mode for delegate/fire: `plan` \| `default` \| `acceptEdits` \| `bypassPermissions`.
`CLAUDE_BRIDGE_TIMEOUT_MS`	`600000`	Per-call timeout for sync tools (`ask`, `delegate`).
`CLAUDE_BRIDGE_SHORT_TIMEOUT_MS`	`30000`	Timeout for `fire` / `check`.

Security: acceptEdits lets delegated Opus edit files autonomously; bypassPermissions additionally allows unrestricted shell. Only raise this for trusted workspaces. ask always uses plan (read-only).

Develop

npm test       # vitest — unit tests for arg building / json parsing
npm run dev    # run from source via tsx

License

MIT

Available Tools

4 tools

adversarial_reviewA

Get an adversarial code/plan review from Claude. Claude hunts for bugs, edge cases, security issues, race conditions and unstated assumptions. USE THIS before merging or committing. Read-only: Claude is instructed not to modify files.

Inputs: content, files, focus, cwd, +2 more.

delegateA

Delegate a complete task to Claude Code running headless (claude -p). Claude has full tool access (read, edit, shell, web) in the given cwd and runs its own agentic loop. Use for heavy autonomous work: refactors, multi-file implementation, running and fixing tests.

Inputs: prompt (required), cwd, model, effort.

follow_upA

Continue a previous Claude session by session_id (returned by every other tool). The prior context lives on Claude's side, so you don't resend it.

Inputs: session_id (required), question (required), cwd, model, +1 more.

web_lookupA

Delegate a web/documentation lookup to Claude (with web access): library docs, API references, error messages, current versions. Use when you need information that may be newer than your training data.

Inputs: query (required), cwd, model, effort.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored 2026-06-22 20:30 across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: adversarial_review for code review, delegate for autonomous tasks, follow_up for session continuation, and web_lookup for web searches. No overlap is apparent.

Naming Consistency4/5

All tools use snake_case, with a mix of verb_noun (delegate, follow_up), adjective_noun (adversarial_review), and noun_verb (web_lookup). The pattern is mostly consistent but not perfectly uniform.

Tool Count5/5

With 4 tools, the set is well-scoped for a delegation bridge server. Each tool earns its place, covering review, autonomous execution, session management, and web lookup.

Completeness4/5

The tool surface covers key delegation scenarios: code review, autonomous work, session continuation, and web research. A minor gap is a simple chat or query tool, but the core use cases are addressed.

Maintenance

ActivityInactive

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Flowra
io.github.flowradev
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Agent Orchestration Autonomous Agents
11
https://mcp.flowra.dev/mcp
SubstrateB
co.trysubstrate
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Developer Tools Knowledge & Memory
131
https://app.trysubstrate.co/mcp
microservices.sh
sh.microservices
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud Platforms Agent Orchestration Developer Tools
21
https://api.microservices.sh/mcp
Kijito
ai.kijito
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Agent Orchestration Knowledge & Memory Communication
1
https://api.kijito.ai/mcp

Related MCP Servers

cc-agent
Autonomous Agents Coding Agents Version Control
Gonzih
A
license
A
quality
D
maintenance
MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
Updated 5 months ago (2026-06-21 20:37 UTC)
47
76 npm
2
Apache 2.0
agent-network
Agent Orchestration Communication Coding Agents
sharifli4
A
license
Not graded
quality
D
maintenance
MCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.
Updated 8 months ago (2026-03-13 07:21 UTC)
MIT
claude-bridge-mcp
Code Execution Coding Agents Developer Tools
millanrp25-dot
A
license
Not graded
quality
D
maintenance
An MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.
Updated 3 months ago (2026-08-08 22:06 UTC)
14 npm
MIT
claude-for-hermes
Coding Agents Autonomous Agents Command Line
7D-codes
A
license
Not graded
quality
D
maintenance
A local MCP server that lets Hermes supervise Claude Code, delegating focused coding, research, or review tasks to the Claude Code CLI and managing worker sessions, background jobs, cancellations, and read-only reviews.
Updated 3 months ago (2026-08-06 13:39 UTC)
3
MIT