Codex Control PlaneSAFE
Durable MCP control plane for long-running Codex Desktop tasks
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/aresyn-codex-control-plane-mcp)
English | Русский
[](https://github.com/aresyn/codex-control-plane-mcp/actions/workflows/ci.yml) [](https://pypi.org/project/codex-control-plane-mcp/) [](https://www.python.org/) [](LICENSE) [](docs/API_CONTRACT.md)
Reliable Codex Desktop automation for long tasks.
codex-control-plane-mcp turns Codex Desktop and codex-app-server into a durable worker that an MCP client can drive safely. Send a task, get an operationId or workflowId right away, poll until the work finishes, approve Plan Mode when needed, then read the final report.
The server handles the awkward parts that thin wrappers usually leave to the caller: app-server startup, thread and turn creation, retry safety, duplicate prompt protection, Plan Mode, approvals, local history, diagnostics, and repair.
OpenClaw and Hermes are first-class clients, but the server is useful for any local orchestrator that needs Codex Desktop to do long-running work without holding one MCP call open for hours.
The short version
MCP client / orchestrator -> submit a task or start a Plan Mode workflow <- receive operationId or workflowId immediately -> poll status -> answer approvals or approve the plan <- read final report, dia
de69130e2db1OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add codex-control-plane-mcp -- None codex-control-plane-mcp==0.2.1
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (4 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (4)
label = f"\nЭто {chunk_label}." if chunk_label else ""left = normalize_prompt(" Нужно\r\nпроверить ПРОЕКТ и подготовить план внедрения идемпотентности. ")assets/repo_image.png
Gates applied: no_behavioural_pass.
de69130e2db1full audit observations/trust-audit/mcp-server/aresyn__codex-control-plane.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | de69130e2db1 | SAFE | B | 89 | first audit |
Questions
What is the Codex Control Plane MCP server?
Durable MCP control plane for long-running Codex Desktop tasks
Is Codex Control Plane safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Codex Control Plane need?
It reads CODEX_API_KEY, DEEPSEEK_API_KEY, DEEPSEEK_MAX_SUMMARY_TOKENS and OPENAI_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Codex Control Plane run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as codex-control-plane-mcp.
How current is this page?
The grade is for one exact copy of the source (de69130e2db1), read on 2026-10-07. The repository is watched and re-audited when it changes.