Codex Control Plane M… vs Claude MCP Bridge | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codex Control Plane MCP vs Claude MCP Bridge
In-depth architectural comparison of the Codex Control Plane MCP and Claude MCP Bridge MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Codex Control Plane MCP
Coding Agents · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Claude MCP Bridge
Coding Agents · Local stdio
Quality: 64/100 (Good) | Auth: other
Verdict Summary: Choose Codex Control Plane MCP if you need specialized Coding Agents tools running via a local process. Choose Claude MCP Bridge if your workspace requires Coding Agents integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Codex Control Plane MCP when:
You need dedicated capabilities in the Coding Agents domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Durable control plane for long-running Codex Desktop tasks. Submit tasks asynchronously, poll operation/workflow state, approve Plan Mode, recover retries, and use hook-backed SQLite history for search and diagnostics.
Wraps Claude Code CLI as MCP tools (query, search, structured, sessions) with subscription-first auth, cost metadata, budget caps, and granular tool sandboxing.
Category & Scope
Tools & Capabilities Breakdown
Codex Control Plane MCP Tools (38)
codex_list_projects
List 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_chats
List 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_chats
List 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_chats
Search 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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Codex Control Plane MCP is categorized under Coding Agents and uses a local stdio subprocess. In contrast, Claude MCP Bridge belongs to Coding Agents using local stdio subprocess. Select Codex Control Plane MCP when you need capabilities focused on coding agents and Claude MCP Bridge when you require tools for coding agents.
Read 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_chat
Read 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_message
Compatibility 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_chat
Compatibility 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_workflow
Start 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_workflow
Start 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_status
Poll 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_plan
Adopt 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 tools listed on main page
Claude MCP Bridge Tools (5)
query
Execute a prompt via Claude Code CLI with optional file context and session resume. Claude is an AI coding agent that can generate, analyze, refactor, and explain code.
Capabilities: code generation and refactoring, code analysis and explanation, file understanding (text and images), multi-turn conversations via sessionId.
Cost: Default model is Sonnet (~$0.01-0.10/call). Use effort="low" for simple tasks, effort="high" + model="opus" for complex analysis. Set maxBudgetUsd to cap per-call cost (recommended for effort="max" or model="opus").
Tips:
- Set workingDirectory to the target repo for project-aware responses.
- Break complex tasks into focused prompts rather than one large request.
- Resume multi-turn conversations with sessionId from a previous response's metadata.
- Include relevant files via the files parameter for targeted context (text files inlined in prompt, images trigger allowed-tools mode).
- Use noSessionPersistence=true for stateless one-shot calls.
structured
Generate JSON conforming to a provided JSON Schema. Uses Claude CLI's native --json-schema flag for validated output (not client-side validation).
Use for: data extraction from text/files, classification, entity parsing, or any task needing machine-parseable output.
Cost: Similar to query (~$0.01-0.10/call). Schema complexity doesn't significantly affect cost.
Tips:
- Pass the JSON Schema as a JSON string in the schema parameter.
- Schema max size: 20KB. Keep schemas focused for reliable output.
- For extraction tasks, include source text via the files parameter or inline in the prompt.
search
Web search via Claude Code CLI using WebSearch and WebFetch tools. Searches the web and synthesizes a comprehensive answer with source URLs.
Use for: current information, documentation lookups, API references, comparing libraries, and research questions.
Cost: Typically ~$0.02-0.05/search with Sonnet.
Tips:
- Ask specific, focused questions for best results.
- Results include source URLs for verification.
- Use maxResponseLength to control response verbosity.
- Increase timeout for complex research queries that may require multiple web fetches.
listSessions
List active Claude CLI sessions tracked by this server. Returns session metadata (IDs, models, timing, turn counts, cumulative cost) for orchestration. Use to check available sessions before resuming with sessionId. No cost (local lookup only).
ping
Health check: verifies Claude CLI is installed and authenticated, reports versions, capabilities, and configuration. No cost (local check only).