Codex Mcp Server
@x51xxx
About Codex Mcp Server
No overview available yet
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"codex-cli": {
"command": "npx",
"args": [
"-y",
"@trishchuk/codex-mcp-tool"
]
}
}
}Tools
13Execute Codex CLI with file analysis (@syntax), skills ($syntax), model selection, and safety controls. Supports changeMode.
Delegate multiple atomic tasks to Codex for batch processing. Ideal for repetitive operations, mass refactoring, and automated code transformations
Run a code review against the current repository using Codex CLI native review subcommand
Echo
receive help information
Display version and system information
Generate creative ideas using structured frameworks with domain context and feasibility analysis.
Retrieves cached chunks from a changeMode response. Use this to get subsequent chunks after receiving a partial changeMode response.
Test timeout prevention by running for a specified duration
List all active conversation sessions with metadata, or manage sessions
Check Codex CLI and session health status
Discover available Codex skills from .agents/skills/ directory
Execute task via Codex, verify with shell command, auto-fix on failure. Act-Check-Fix loop.
Overview
What is Codex MCP Server?
An MCP server that connects Claude or Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode. It is for developers who want to leverage Codex CLI’s capabilities through an MCP-compatible client.
How to use Codex MCP Server?
Install and add via claude mcp add codex-cli -- npx -y @trishchuk/codex-mcp-tool or configure in claude_desktop_config.json. Prerequisites: Node.js 18+ and a working Codex CLI installation (authenticated). Invoke tools like ask-codex, brainstorm, list-sessions, or health.
Key features of Codex MCP Server
- File analysis with
@file references - Multi-turn conversations with workspace isolation
- Native resume using
codex resume(CLI v0.36.0+) - Local OSS model support via Ollama or LM Studio
- Sandboxed code execution with
--full-auto - Structured brainstorming with SCAMPER framework
Use cases of Codex MCP Server
- Analyze code architecture by referencing files via
@src/ - Conduct multi-turn code review sessions using session IDs
- Run untrusted code safely in sandbox mode
- Generate refactoring ideas with structured brainstorming
- Use local models for code analysis without sending data to OpenAI
FAQ from Codex MCP Server
What are the runtime dependencies?
Node.js 18+ and a locally installed and authenticated Codex CLI are required.
How do I configure multi-turn conversations?
Pass a sessionId parameter in your prompt. Sessions persist for 24 hours by default (configurable via CODEX_SESSION_TTL_MS), with a maximum of 50 sessions.
What models are supported?
By default the CLI’s configured model is used. You can override with model names like gpt-5.5, gpt-5.4, gpt-5.4-mini, or use local OSS models via localProvider: "ollama" or "lmstudio".
Where does session data live?
Session data is stored locally on your machine under the Codex CLI workspace; no data is sent to external servers except through your chosen model provider.
What CLI versions are compatible?
Features work best with Codex CLI v0.36.0+ (sessions), v0.52.0+ (search), and v0.59.0+ (add-dirs, token limits).
Frequently asked questions
What are the runtime dependencies?
Node.js 18+ and a locally installed and authenticated Codex CLI are required.
How do I configure multi-turn conversations?
Pass a `sessionId` parameter in your prompt. Sessions persist for 24 hours by default (configurable via `CODEX_SESSION_TTL_MS`), with a maximum of 50 sessions.
What models are supported?
By default the CLI’s configured model is used. You can override with model names like `gpt-5.5`, `gpt-5.4`, `gpt-5.4-mini`, or use local OSS models via `localProvider: "ollama"` or `"lmstudio"`.
Where does session data live?
Session data is stored locally on your machine under the Codex CLI workspace; no data is sent to external servers except through your chosen model provider.
What CLI versions are compatible?
Features work best with Codex CLI v0.36.0+ (sessions), v0.52.0+ (search), and v0.59.0+ (add-dirs, token limits).
Basic information
More Developer Tools MCP servers

directree
coburn2716directree MCP server — query the honest software directory from any AI assistant

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Termany
thinkany-aiAgent-Native Terminal
ZeroBeacon — 1000-Tool Collision-Proof Commerce Router
DavidFox998ZeroBeacon.ai — Collision-proof commerce router for AI agents. 1000 MCP tools: commerce, trust, billing, sovereign ID + everyday tools. LIVE.

Apiosk
obcraftAI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·
Comments