agent-bridge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-bridgeStart Claude and Codex on separate worktrees for issues 42 and 43."
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.
Agent Bridge
Work with Claude Code and Codex in separate terminals without losing track of who owns what. Agent Bridge gives each agent a Git worktree and a shared place for issue claims, file reservations, messages, and handoffs.
The coordination engine is built in-house with Python's standard library. It has no runtime dependencies and makes no model calls. Your existing Claude and Codex logins and permission settings still apply.
Get started
Requires Linux with pidfd support, Git, uv, and signed-in
claude and codex commands. Python 3.12+ is installed by uv if needed.
git clone https://github.com/suneel944/agent-bridge.git
cd agent-bridge
make installThen, from any directory, open two terminals:
# Terminal 1
agent-bridge run claude --repo /path/to/your/repo --task "Work on issue 42"
# Terminal 2
agent-bridge run codex --repo /path/to/your/repo --task "Work on issue 43"Start from a committed, clean checkout. The launcher creates both worktrees;
the agents claim issues from their assigned lanes. Run agent-bridge status
to see ownership, recent activity, and reported results.
Related MCP server: coordinaut
How it fits together
flowchart TD
Repo[Your repository] --> Bridge[Agent Bridge launcher]
Bridge --> Claude[Claude Code · own worktree]
Bridge --> Codex[Codex · own worktree]
Claude <-->|Six scoped MCP tools| Server[Local coordination service]
Codex <-->|Six scoped MCP tools| Server
Server --> DB[(SQLite WAL · mail and reservations)]
Claude --> Claims[Atomic issue claims and handoffs]
Codex --> Claims
DB --> Hooks[Native checkpoints · bounded updates]
Claims --> Hooks
Hooks -.-> Claude
Hooks -.-> CodexIssue ownership changes only through explicit claims and accepted handoffs. Conflicting file reservations grant nothing. Hooks deliver short updates when state changes; unchanged checkpoints add no context. Each notice is capped at 1,536 UTF-8 bytes, and full message bodies are fetched only when needed.
Worktrees and reservations are coordination boundaries, not OS sandboxes. Agent Bridge does not merge branches, approve commands, or wake idle agents. Token usage still depends on the native agents; the bridge reports injected bytes rather than claiming a universal token-saving percentage.
Plugins and releases
Claude Code and Codex plugins share the same coordination skill. Installation, upgrades, and marketplace details are in Operations. Download packages, plugin bundles, changelogs, and checksums from Releases.
Contributing
Run make check before opening a PR. It checks formatting, lint, typing,
documentation rules, package builds, and behavior tests.
See Contributing, Architecture, Security, and the Code of Conduct. Agent Bridge is available under the MIT license.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
- ParleyOAuthdev.weldra
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceShare context, detect file conflicts, and send messages across parallel Claude Code sessions83MIT
- AlicenseNot gradedqualityAmaintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.MIT
- AlicenseNot gradedqualityAmaintenanceLocal coordination for coding agents that share a Git working tree.122MIT
- AlicenseNot gradedqualityBmaintenanceEnables peer-to-peer communication between Claude Code sessions, allowing them to send messages, hand off tasks, and coordinate across worktrees without manual intervention.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/suneel944/agent-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server