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. |
Capabilities
Features and capabilities supported by this server
| 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 | |
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/WebisityStudio/claude-codex-mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server