codex-cli-mcp
Bridges OpenAI Codex CLI to any MCP client, allowing headless Codex sessions via tools like codex and codex-reply.
README
<div align="center">
<picture> <img alt="codex-cli-mcp" src="docs/images/banner.svg" width="100%"> </picture>
Bridge OpenAI Codex CLI to any MCP client
English | 한국어
<a href="https://www.npmjs.com/package/@nayagamez/codex-cli-mcp">npm</a> · <a href="https://github.com/nayagamez/codex-cli-mcp">GitHub</a> · <a href="https://github.com/nayagamez/codex-cli-mcp/issues">Issues</a>
</div>
Overview
An MCP (Model Context Protocol) server that wraps OpenAI Codex CLI as tools. It enables MCP clients like Claude Desktop, Cursor, and Windsurf to run Codex CLI sessions in headless mode.
Prerequisites
1. Install Codex CLI
Install Codex CLI (docs) and make sure it is available in your PATH:
# npm
npm install -g @openai/codex
# Homebrew (macOS)
brew install --cask codex
Or download the binary from GitHub Releases.
2. Authenticate
Option A — ChatGPT Login (Recommended)
Run codex and select "Sign in with ChatGPT". Requires a Plus, Pro, Team, Edu, or Enterprise plan.
Option B — API Key
For headless / CI environments:
export OPENAI_API_KEY="your-api-key"
See the Codex Authentication docs for more details.
Tools
See Codex Models for available models.
codex
Start a new Codex CLI session.
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt |
string | Yes | The prompt to send to Codex |
model |
string | No | Model name override |
effort |
enum | No | Reasoning effort: medium, high, xhigh (auto-selected by task complexity) |
sandbox |
enum | No | read-only, workspace-write, or danger-full-access |
cwd |
string | No | Working directory for the session |
profile |
string | No | Configuration profile from config.toml |
config |
object | No | Config overrides as key-value pairs |
timeout |
number | No | Timeout in ms (default: 600000 = 10 min) |
codex-reply
Continue an existing Codex CLI session.
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt |
string | Yes | The follow-up prompt |
threadId |
string | Yes | Thread ID from a previous codex call |
model |
string | No | Model name override |
effort |
enum | No | Reasoning effort: medium, high, xhigh (auto-selected by task complexity) |
config |
object | No | Config overrides as key-value pairs |
timeout |
number | No | Timeout in ms (default: 600000 = 10 min) |
Setup
For Humans
Copy the prompt below and paste it into your LLM agent — it will install and configure everything automatically:
Install and configure @nayagamez/codex-cli-mcp by following: https://raw.githubusercontent.com/nayagamez/codex-cli-mcp/main/docs/guide/installation.md
Or set it up manually — see Manual Setup below.
For LLM Agents
curl -s https://raw.githubusercontent.com/nayagamez/codex-cli-mcp/main/docs/guide/installation.md
Manual Setup
<details> <summary>Claude Desktop</summary>
Add to your claude_desktop_config.json:
{
"mcpServers": {
"codex-cli-mcp": {
"command": "npx",
"args": ["-y", "@nayagamez/codex-cli-mcp"]
}
}
}
</details>
<details> <summary>Cursor / Windsurf</summary>
Add to your MCP settings:
{
"mcpServers": {
"codex-cli-mcp": {
"command": "npx",
"args": ["-y", "@nayagamez/codex-cli-mcp"]
}
}
}
</details>
<details> <summary>Claude Code</summary>
claude mcp add codex-cli-mcp -- npx -y @nayagamez/codex-cli-mcp
</details>
Progress Notifications
The server sends MCP progress notifications in real-time as Codex processes your request. This lets MCP clients know the server is alive and working, not hanging.
Progress messages include:
[5s] Session started (thread: ...)— session initialized[12s] Command executed: npm test— a command was run[18s] Message: Refactoring the auth module...— agent reasoning[25s] Turn completed— turn finished
Idle-based Timeout
The timeout is idle-based, not absolute. The timer resets every time the server receives an event from Codex. This means long-running tasks with continuous activity will never timeout, while truly stuck processes will be killed after the configured idle period.
- Default idle timeout: 10 minutes
- Override per-call via
timeoutparameter, or globally viaCODEX_TIMEOUT_MS
Environment Variables
| Variable | Default | Description |
|---|---|---|
CODEX_CLI_PATH |
codex |
Path to the Codex CLI binary |
CODEX_TIMEOUT_MS |
600000 (10 min) |
Idle timeout for Codex process |
CODEX_MCP_DEBUG |
(unset) | Set to enable debug logging to stderr |
How It Works
MCP Client → Tool Call (codex / codex-reply)
→ Spawn `codex exec --json --full-auto` as subprocess
→ Stream JSONL events from stdout
→ Send progress notifications back to client
→ Return formatted results when done
- The MCP client sends a tool call (
codexorcodex-reply) - The server spawns Codex CLI with
--jsonand--full-autoflags - The prompt is passed via stdin
- JSONL events are streamed and parsed in real-time
- Progress notifications are sent to the client on each event (idle timer resets)
- Results (messages, commands, errors, token usage) are formatted as markdown and returned
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.