Codex Control Plane MCP
Related Servers
Alternatives to Codex Control Plane MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables durable, retry-safe automation of long-running Codex Desktop tasks through asynchronous operations and workflows, with polling, approvals, Plan Mode, diagnostics, and recovery.-
- FlicenseNot gradedqualityAmaintenanceEnables durable, retry-safe automation of long-running Codex Desktop tasks through MCP, with async operations, polling, Plan Mode workflows, approvals, diagnostics, and restart recovery.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to submit, monitor, approve, and recover long-running Codex Desktop tasks without blocking for hours. It provides retry-safe operations, Plan Mode workflows, diagnostics, and central worker coordination for durable automation.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive Codex Desktop and codex-app-server as a durable asynchronous worker for long-running tasks, with polling, approvals, Plan Mode workflows, retry safety, diagnostics, and final reporting. It also provides recovery, queueing, and repair tools for reliable local automation.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit and manage durable, asynchronous Codex Desktop tasks, including polling, approvals, Plan Mode workflows, and final reports. It provides retry-safe operations, recovery, diagnostics, and local state for reliable long-running automation.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive Codex Desktop as a durable asynchronous worker for long-running tasks, including submitting operations or workflows, polling status, managing approvals and Plan Mode, and reading final reports. It also provides retry safety, duplicate-prompt protection, restart recovery, and diagnostics for reliable local automation.-
TDQS
Scored across 38 tools
Each tool has a clearly distinct purpose with detailed descriptions that specify when to use it and what to do next. Overlaps like codex_execute_plan vs codex_approve_plan are resolved by marking the former as a compatibility wrapper. No two tools perform the same action.
All tools follow the consistent pattern codex_<verb>_<noun> with lowercase and underscores. Verbs like get, list, start, submit are used uniformly, and there is no mixing of styles.
38 tools is high but each serves a distinct operation within the control plane domain, covering workflow lifecycle, diagnostics, chat, worker, and project management. A few redundancies exist for backward compatibility, but overall the count is justified by the breadth of functionality.
The tool surface covers the complete lifecycle: health checks, diagnostics, planning, execution, review, chat management, project discovery, and cleanup (archive/unarchive). Missing operations like deletion are not essential for a control plane, and the set provides no dead ends for common workflows.