About Codex Dev
Codex Dev is an MCP server published by FYZAFH in the Developer Tools category: mCP Server for Codex CLI integration - stateful code writing and review workflows.
The repository has 166 stars and 18 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/FYZAFH/mcp-codex-devThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (6)
execClean dialogue without templates, supports session resume
Parameters not published.
healthEnvironment and config diagnostics
Parameters not published.
reviewCode review (spec + quality in parallel), supports resume
Parameters not published.
session_discardDiscard sessions
Parameters not published.
session_listList tracked sessions
Parameters not published.
tddCodex CLI with built-in test-driven development prompt template
Parameters not published.
Ask AI
Ask AI about Codex Dev
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- !No dynamic code executionSource scan found eval or shell execution. Review how tool inputs reach it before granting credentials.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
mcp-codex-dev
MCP Server for integrating Codex CLI into Claude Code workflows with session management and real-time progress monitoring.
Installation
Prerequisites: Codex CLI installed and configured.
In .mcp.json file
{
"mcpServers": {
"mcp-codex-dev": {
"command": "npx",
"args": ["-y", "mcp-codex-dev"]
}
}
}
or
claude mcp add mcp-codex-dev -- npx -y mcp-codex-dev
Windows OS:
{
"mcpServers": {
"mcp-codex-dev": {
"command": "cmd",
"args": ["/c", "npx", "-y", "mcp-codex-dev"]
}
}
}
or
claude mcp add mcp-codex-dev -- cmd /c npx -y mcp-codex-dev
Tools
| Tool | Description |
|---|---|
exec |
Clean dialogue without templates, supports session resume |
tdd |
Codex CLI with built-in test-driven development prompt template |
review |
Code review (spec + quality in parallel), supports resume |
health |
Environment and config diagnostics |
session_list |
List tracked sessions |
session_discard |
Discard sessions |
Configuration
Create ~/.mcp/mcp-codex-dev/config.json:
{
"model": "gpt-5.2",
"sandbox": "danger-full-access",
"timeout": 300000,
"tools": {
"tdd": { "model": "gpt-5.3-codex", "sandbox": "danger-full-access", "timeout": 2000000},
"review": { "model": "gpt-5.2", "sandbox": "danger-full-access", "timeout": 3000000},
"health": { "enabled": false }
}
}
Top-level model / sandbox / timeout are global defaults. The tools section overrides per tool (keyed by tool name). Set "enabled": false to disable a tool.
Per-project config can be placed at <project>/.mcp/mcp-codex-dev.config.json.
Progress Server
A local HTTP server starts at http://localhost:23120 showing real-time progress. Configurable via progressPort.
When multiple MCP server instances run simultaneously, they share a single progress page: the first instance binds the port and serves the UI, and other instances forward their progress events to it.
Session Tracking
Session tracking metadata is stored per project at <project>/.mcp/mcp-codex-dev/sessions.json (where <project> is the Git repo root if applicable).
Codex CLI's own session files remain in ~/.codex/sessions/<id>/.
License
No license.
README fetched from the repository 5 days ago. The original is authoritative.