Claude Code Bridge
Let Claude Code instances on different machines relay messages through named MCP channels while you run split dev setups or paired agent workflows.
Overview
Claude Code Bridge is an MCP server for the Build phase that relays messages between Claude Code agents on different machines using named channels and shared SQLite state.
What is this MCP server?
- stdio MCP package via uvx (claude-code-bridge 0.9.1 on PyPI)
- Named channels for message exchange between Claude Code agents on separate hosts
- Shared SQLite state via CLAUDE_BRIDGE_DB across HTTP and stdio instances
- Optional CLAUDE_BRIDGE_AUTH_TOKEN Bearer protection for HTTP mode (not stdio)
- Runtime positional flag --stdio for local MCP transport
- Version 0.9.1
- Transport: stdio via uvx; HTTP mode documented with optional Bearer auth
- Two configurable env vars: CLAUDE_BRIDGE_DB, CLAUDE_BRIDGE_AUTH_TOKEN
Community signal: 8 GitHub stars.
What problem does it solve?
Running Claude Code on more than one machine leaves you copying prompts and results by hand instead of a simple agent-to-agent message path.
Who is it for?
Indie hackers with multi-machine Claude Code setups who want a minimal MCP relay before investing in heavier orchestration.
Skip if: Builders who only use a single local Claude Code session or need enterprise message queues with deduplication and DLQs out of the box.
What do I get? / Deliverables
After you configure uvx stdio (and optional shared DB or HTTP with auth), agents can post and read on shared channels without leaving MCP.
- Named MCP channels for cross-machine Claude Code messaging
- Optional unified bridge state when HTTP and stdio share CLAUDE_BRIDGE_DB
- HTTP endpoints securable with Bearer auth outside /status
Recommended MCP Servers
Journey fit
Cross-machine agent messaging is part of how you assemble and operate multi-agent dev environments during the Build phase. The server exists specifically to extend Claude Code with relay tooling, which belongs on the agent-tooling shelf rather than generic backend code.
How it compares
Lightweight MCP message relay, not a full multi-agent framework or team chat product.
Common Questions / FAQ
Who is Claude Code Bridge for?
Solo builders and small teams running Claude Code on multiple machines who need named channels for agent-to-agent messages.
When should I use Claude Code Bridge?
Use it during Build when you split agent work across devices and want MCP-native send/receive instead of manual context sync.
How do I add Claude Code Bridge to my agent?
Register the PyPI package with uvx, pass --stdio for MCP transport, set CLAUDE_BRIDGE_DB if sharing state, and add optional CLAUDE_BRIDGE_AUTH_TOKEN for HTTP.