mcp-codex-dev
An MCP server that integrates Codex CLI into Claude Code workflows, providing session-managed tools for executing Codex actions (including TDD and review) and exposing auxiliary tools like health checks and session listing/discarding. It can also start a local HTTP progress UI server and stores MCP session tracking metadata per project.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No authentication/authorization controls are described. The server starts a local HTTP progress page, which implies possible plaintext exposure on localhost (TLS not mentioned). The README indicates local disk writes for session metadata and references per-tool sandbox/model settings; without more detail, secret handling and access controls cannot be verified. Dependency hygiene is unknown beyond listed dependencies (TypeScript SDK and zod).
⚡ Reliability
Best When
You want an agent/IDE integration that can orchestrate Codex CLI operations with resumable sessions and a local progress UI on a developer machine.
Avoid When
You cannot allow writing session metadata to disk under project directories or you require enterprise-grade security guarantees with documented auth, TLS, and secrets handling.
Use Cases
- • Stateful code generation and continuation via Codex CLI sessions inside an MCP-enabled IDE workflow
- • Code review workflows with a structured review tool and resumable sessions
- • Running Codex-based TDD prompts and tracking progress within an agent workflow
- • Debugging/config verification via a health diagnostics tool
- • Managing and cleaning up tracked Codex sessions per project
Not For
- • Production deployments where local filesystem/session persistence and local HTTP UI hosting are unacceptable
- • Environments requiring formal SLAs, strong backward-compat guarantees, or documented operational policies
- • Teams needing a well-specified, externally authenticated API surface (no auth scheme is described here)
Interface
Authentication
No authentication mechanism is described in the provided README. The integration appears to rely on local configuration files and the host agent/IDE (Claude Code) invoking the MCP tools.
Pricing
No pricing information provided.
Agent Metadata
Known Gotchas
- ⚠ Progress UI is served from a local port (default 23120) with special handling when multiple MCP instances run; orchestration may need to account for port conflicts and event forwarding.
- ⚠ Session tracking metadata is stored per project; agents should avoid excessive session creation without cleanup.
- ⚠ Tool behaviors (especially exec/review/resume semantics) depend on Codex CLI session mechanics; ensure the model/sandbox/timeouts are configured consistently per tool.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-codex-dev.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.