Claude Codex Bridge vs Codex Control Plane MCP
A side-by-side look at the Claude Codex Bridge and Codex Control Plane MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Claude Codex BridgeCoding AgentsRun Codex agents from Claude Code through MCP and Channels, with live progress notifications, mid-task steering and session continuation.49FairAuth: not declaredVerdict: choose Claude Codex Bridge for coding agents work; choose Codex Control Plane MCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Claude Codex Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You want tools like
codex_models, codex_start, codex_message.
Choose Codex Control Plane MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
codex_list_projects, codex_list_project_chats, codex_list_active_chats.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Claude Codex Bridge | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 49/100 · Fair | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 125 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 8 | 38 |
| Full listing | View Claude Codex Bridge | View Codex Control Plane MCP |
Tools & capabilities
Claude Codex Bridge tools 8
codex_modelsList the models available to Codex.codex_startStart an independent task in an absolute project directory.codex_messageSend an instruction during a turn, or start the next turn.codex_stopInterrupt the current turn.codex_resumeReopen a saved Codex thread.codex_answerAnswer a structured question from Codex.codex_statusRead status, pending questions, and the latest answer.codex_eventsRead recent events using a sequence cursor.
Codex Control Plane MCP tools 38
codex_list_projectsList known Codex projects from registry, hook history, transcripts, and cached Codex state. Use this before preflight or submit when you need a project reference; later tools accept projectId, project name, or project path and return canonical projectId. Next call codex_preflight_project_run for a concrete project.codex_list_project_chatsList chats for one project from the bounded read model. Use this to find existing threads before continuation or review. Next call codex_get_chat_status, codex_get_chat, or codex_submit_task.codex_list_active_chatsList chats that look active from tracked, hook, transcript, or cached evidence. Use this for operator inspection, not for creating retries. Next call codex_get_turn_status or codex_get_operation_status when ids are available.codex_search_chatsSearch chat history through the MCP-owned index and safe fallback sources. Use this for discovery or recovery when ids were lost. Do not use search results as proof that a turn is still active.codex_get_chat_statusRead lightweight chat status and safe previews. Use this to inspect a known thread without starting live work. Next call codex_get_chat for content or codex_submit_task for a new operation.codex_get_chatRead bounded chat content from hook history, transcripts, or legacy fallback. Use this for context recovery and final report inspection. It is not a write path and should not trigger retries.codex_send_messageCompatibility write for sending a message to an existing Codex thread. Prefer codex_submit_task with operation_type='send_message' for durable long work. In client mode this delegates to the durable queue.codex_start_chatCompatibility write for starting a new Codex chat. Prefer codex_submit_task with operation_type='start_chat' for durable long work. In client mode this delegates to the durable queue.codex_start_plan_workflowStart a durable Plan Mode workflow and return workflowId immediately. Use this when a plan must be prepared before implementation. Next poll codex_get_workflow_status, then call codex_approve_plan when latestPlan is ready.codex_start_review_workflowStart a durable Codex review workflow and return workflowId immediately. Use this for code review tasks. Next poll codex_get_workflow_status for progress and final report.codex_get_workflow_statusPoll workflow state from storage by default. Use this for Plan Mode, execution, and review workflows. Follow nextRecommendedAction and do not create replacement work unless guidance tells you to.codex_adopt_workflow_planAdopt a valid newer Plan Mode candidate already present in the workflow thread. Use this only when status or diagnostics reports an adoptable plan. Next poll codex_get_workflow_status.- +26 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Claude Codex Bridge
No confirmed install command for Claude Codex Bridge yet — follow the setup steps linked from its listing page rather than a guessed package name.
Codex Control Plane MCP
{
"mcpServers": {
"aresyn-codex-control-plane-mcp": {
"command": "uvx",
"args": [
"codex-control-plane-mcp"
]
}
}
}
Frequently asked questions
Claude Codex Bridge is categorized under Coding Agents and uses an install path we have not confirmed yet. Codex Control Plane MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Claude Codex Bridge for coding agents work and Codex Control Plane MCP for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Claude Codex Bridge has no confirmed install command yet — follow its own setup instructions.
Claude Codex Bridge is bring-your-own-key: usage is billed by the API provider you supply a key for. Codex Control Plane MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add umum-ai-claude-codex-bridge and aresyn-codex-control-plane-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Claude Codex Bridge has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 10 GitHub stars. Codex Control Plane MCP has 63/100 (Good) with 4 views, 0 installs and 125 GitHub stars.