codex-claude-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_CLAUDE_BRIDGE_DATA_DIR | No | Absolute path to the shared bridge data directory. Defaults to ~/.codex-claude-bridge if not set. | ~/.codex-claude-bridge |
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 |
|---|---|
| create_taskB | Create a shared task that either Codex or Claude Code can claim. |
| list_tasksB | List tasks in the shared coordination board. |
| claim_taskA | Claim an open task before starting work; prevents duplicate ownership. |
| update_taskB | Update a task's status, owner, or final result. |
| post_messageB | Send a message to the other agent, optionally attached to a task. |
| read_messagesA | Read shared messages, optionally filtering for a task or recipient. |
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 6 tools
Each tool targets a distinct action: creating, listing, claiming, updating tasks, and posting/reading messages. There is no overlap or ambiguity between any two tools.
All tool names follow a consistent verb_noun pattern (create_, list_, claim_, update_, post_, read_). The naming is predictable and uniform.
Six tools is a well-scoped size for a coordination bridge. Each tool earns its place and covers a necessary function without bloat.
The tool set covers the full task lifecycle (create, list, claim, update) and messaging (post, read). A minor gap is the absence of a dedicated get_task or delete/archive mechanism, but update_task can handle status changes.