Skip to content
Back to search

mcp-codex-dev

SkillWorks with CodexGitHub

MCP Server for Codex CLI integration - stateful code writing and review workflows

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fyzafh--mcp-codex-dev/badge.svg)](/listings/fyzafh--mcp-codex-dev)

HTML

<a href="/listings/fyzafh--mcp-codex-dev"><img src="/api/listings/fyzafh--mcp-codex-dev/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites: [Codex CLI](https://github.com/openai/codex) 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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 97 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # mcp-codex-dev
  2. <p align="center">English | <a href="README.zh-CN.md">中文</a></p>
  3. MCP Server for integrating [Codex CLI](https://github.com/openai/codex) into Claude Code workflows with session management and real-time progress monitoring.
  4. <img width="1890" height="948" alt="image" src="https://github.com/user-attachments/assets/490a8cf6-1267-42cd-8f6f-e0a82c0dc6a3" />
  5. ## Installation
  6. Prerequisites: [Codex CLI](https://github.com/openai/codex) installed and configured.
  7. In .mcp.json file
  8. ```
  9. {
  10. "mcpServers": {
  11. "mcp-codex-dev": {
  12. "command": "npx",
  13. "args": ["-y", "mcp-codex-dev"]
  14. }
  15. }
  16. }
  17. ```
  18. or
  19. ```bash
  20. claude mcp add mcp-codex-dev -- npx -y mcp-codex-dev
  21. ```
  22. Windows OS:
  23. ```
  24. {
  25. "mcpServers": {
  26. "mcp-codex-dev": {
  27. "command": "cmd",
  28. "args": ["/c", "npx", "-y", "mcp-codex-dev"]
  29. }
  30. }
  31. }
  32. ```
  33. or
  34. ```powershell
  35. claude mcp add mcp-codex-dev -- cmd /c npx -y mcp-codex-dev
  36. ```
  37. ## Tools
  38. | Tool | Description |
  39. |------|-------------|
  40. |`exec`|Clean dialogue without templates, supports session resume|
  41. |`tdd`|Codex CLI with built-in test-driven development prompt template|
  42. | `review` | Code review (spec + quality in parallel), supports resume |
  43. | `health` | Environment and config diagnostics |
  44. | `session_list` | List tracked sessions |
  45. | `session_discard` | Discard sessions |
  46. ## Configuration
  47. Create `~/.mcp/mcp-codex-dev/config.json`:
  48. ```json
  49. {
  50. "model": "gpt-5.2",
  51. "sandbox": "danger-full-access",
  52. "timeout": 300000,
  53. "tools": {
  54. "tdd": { "model": "gpt-5.3-codex", "sandbox": "danger-full-access", "timeout": 2000000},
  55. "review": { "model": "gpt-5.2", "sandbox": "danger-full-access", "timeout": 3000000},
  56. "health": { "enabled": false }
  57. }
  58. }
  59. ```
  60. 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.
  61. Per-project config can be placed at `<project>/.mcp/mcp-codex-dev.config.json`.
  62. ## Progress Server
  63. A local HTTP server starts at `http://localhost:23120` showing real-time progress. Configurable via `progressPort`.
  64. 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.
  65. ## Session Tracking
  66. Session tracking metadata is stored per project at `<project>/.mcp/mcp-codex-dev/sessions.json` (where `<project>` is the Git repo root if applicable).
  67. Codex CLI's own session files remain in `~/.codex/sessions/<id>/`.
  68. ## License
  69. No license.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.