Claude Mcp Bridge
Expose Claude Code CLI as MCP tools so a second agent can query, search, and return structured answers from an existing Claude session.
Overview
Claude MCP Bridge is an MCP server for the Build phase that wraps the Claude Code CLI as query, search, structured, ping, and listSessions tools over stdio.
What is this MCP server?
- MCP tools: query, search, structured, ping, listSessions against Claude Code CLI
- stdio npm package claude-mcp-bridge (v0.6.1)
- Per-tool model overrides via CLAUDE_QUERY_MODEL, CLAUDE_SEARCH_MODEL, CLAUDE_STRUCTURED_MODEL
- CLAUDE_CLI_PATH env for non-default claude binary location
- Shared CLAUDE_DEFAULT_MODEL with per-tool fallback defaults to sonnet
- Package version 0.6.1
- Five documented tools: query, search, structured, ping, listSessions
- Default per-tool models: sonnet for query, search, and structured when unset
Community signal: 2 GitHub stars.
What problem does it solve?
Your primary IDE agent cannot call Claude Code’s CLI capabilities as typed MCP tools without custom subprocess glue.
Who is it for?
Builders running Claude Code on PATH who want another MCP client to drive Claude via query, search, and structured tools.
Skip if: Users without the Claude Code CLI installed or teams that only need a single IDE with no cross-agent delegation.
What do I get? / Deliverables
A stdio MCP server forwards tool calls to the claude binary so orchestrator agents reuse Claude sessions with configurable models.
- Five MCP tools delegating to Claude Code: query, search, structured, ping, listSessions
- Configurable model selection per tool via environment variables
- Cross-host orchestration without rewriting Claude CLI integration
Recommended MCP Servers
Journey fit
Bridging one CLI agent into another host’s tool surface is core build-phase agent tooling for multi-agent or IDE orchestration. stdio npm package that wraps claude with query, search, structured, ping, and listSessions maps cleanly to agent-tooling integrations.
How it compares
CLI-to-MCP bridge, not a standalone coding skill or cloud-hosted model API.
Common Questions / FAQ
Who is Claude MCP Bridge for?
Solo builders and small teams orchestrating multiple MCP-capable tools who already rely on the Claude Code CLI and want it exposed as standard MCP tools.
When should I use Claude MCP Bridge?
Use it during build-phase setup when a host agent must query, search, or structured-call Claude while managing its own session list.
How do I add Claude MCP Bridge to my agent?
Install the npm package claude-mcp-bridge, add it as a stdio MCP server, set CLAUDE_CLI_PATH if needed, and optionally configure CLAUDE_DEFAULT_MODEL or per-tool model variables.