claude-codex-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_BIN | No | Path to the Codex CLI executable. Used when Codex is not available as 'codex' on PATH. | |
| BRIDGE_DB_PATH | No | Absolute path to the SQLite database file. Overrides the default location (~/.local/share/claude-codex-bridge/bridge.sqlite). All MCP processes must point to the same database. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_registerA | Announce an agent and its capabilities so others can discover it. |
| bridge_sendA | Deliver a message to another agent. Use '*' to broadcast to everyone. |
| bridge_inboxA | List messages addressed to an agent. Acknowledged messages are hidden by default. |
| bridge_waitA | Keep this agent turn alive until a matching bridge message arrives. Use this instead of ending the turn and later asking the user to tell you to read the inbox. After handling and replying to the returned message, call bridge_wait again automatically if the coordination thread is still active. This is the MCP push-style handoff: the tool blocks efficiently and returns as soon as the other agent sends. It cannot wake a chat whose turn has already ended, so enter bridge_wait before going idle. |
| bridge_ackA | Mark messages as read for an agent so they drop out of the unread inbox. |
| bridge_threadA | Return the full history of a conversation thread, oldest first. |
| bridge_agentsA | List all registered agents and their capabilities. |
| bridge_orchestrate_codexA | Start a saved Codex worker session in an isolated git worktree and wait for its structured result. If status is waiting_for_fable, the active Claude/Fable coordinator should answer the returned question and immediately call bridge_continue_codex. Independent calls create separate Codex chips. This tool never grants permission to commit, push, deploy, publish, send externally, change credentials, delete data, or mutate production. |
| bridge_continue_codexA | Resume the exact saved Codex session and worktree after Codex asked Fable for help. Call this automatically in the same Claude turn after answering the question returned by bridge_orchestrate_codex. Continue until completed, blocked, failed, or the round limit is reached. |
| bridge_orchestration_statusA | Recover durable run state and its audit events after a restart or when checking progress. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool serves a distinct purpose: messaging tools (send, inbox, ack, wait, thread) are clearly separated from orchestration tools (orchestrate_codex, continue_codex, orchestration_status) and discovery/registration (register, agents). Despite some semantic overlap between inbox and thread, their descriptions make the boundary clear.
All tools share the 'bridge_' prefix, which provides a strong visual pattern, but the suffix style is mixed: some are bare verbs (send, wait, ack), some are nouns (inbox, agents, thread), and some are verb_noun (continue_codex, orchestrate_codex). This is readable but not a consistent verb_noun convention.
10 tools is well within the ideal 3-15 range for a server of this scope. Each tool addresses a clear aspect of agent messaging or Codex orchestration without redundancy or bloat.
The tool surface covers the full coordination lifecycle: registration, discovery, messaging, blocking waits, acknowledgments, thread history, and orchestration state recovery. Minor gaps like an explicit cancel/abort for Codex sessions and a way to list saved sessions are absent but can be worked around with the provided status and continue tools.