In-depth architectural comparison of the Codex Control Plane MCP and Oz MCP Server 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: 63/100 (Good) | Auth: No auth required
Oz MCP Server
Coding Agents · Local stdio
Quality: 61/100 (Good) | Auth: other
Verdict Summary: Choose Codex Control Plane MCP if you need specialized Coding Agents tools running via a local process. Choose Oz MCP Server 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.
Bridges Warp's Oz coding agent to any IDE or MCP client (Claude Code, Cursor, Codex), plus native @oz in VS Code Copilot Chat. Independent project; uses only Warp's documented public interfaces. MIT.
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, Oz MCP Server belongs to Coding Agents using local stdio subprocess. Select Codex Control Plane MCP when you need capabilities focused on coding agents and Oz MCP Server 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
Oz MCP Server Tools (6)
oz_agent_run
Run `oz agent run` locally with a prompt. Returns the full run payload.
oz_agent_run_cloud
Launch a cloud run. **Consumes Warp credits.
oz_run_get
Fetch a run's status and output by id. Read-only.
oz_run_list
List recent runs; filter by `all` / `active` / `completed` / raw status, plus a numeric `limit`.
oz_list_models
List the AI model ids available to the account and report the current default. Read-only.
oz_set_default_model
Set the default Oz model by writing `defaultModel` into the workspace `.warp/warp-bridge.yaml`.