Bridge AI coding hosts to the OpenAI Codex CLI for delegated implementation.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Stop burning your frontier agent's limits on boilerplate.
Delegate implementation to the OpenAI Codex CLI β your agent writes the brief and reviews the diff.
Use your best coding agent where its judgment matters most: understanding the task, shaping the plan, and reviewing the result.
Codex Delegate is the MCP bridge that lets Claude Code, Cursor, Copilot β or any MCP client β hand implementation to the OpenAI Codex CLI, then get a clean, structured result back for review.
Your assistant does what frontier models are actually for: understands the task, writes a precise brief, reviews the finished diff. Codex holds its own as the implementer β guided and checked by a smarter orchestrator. The result reads like frontier work, because a frontier model planned it and signed off on it.
Codex tears through multi-file edits while a frontier chat model would still be streaming the first file. You delegate, keep working with your assistant, and the diff shows up done.
Delegated work runs on the OpenAI Codex CLI and its own usage β separate from your orchestrator's chat quota. Your Claude, Cursor, or Copilot subscription spends tokens on the brief and the review; Codex does the grinding. On API? That's the per-token grind moved off your main bill.


status, the files Codex edited, and per-turn token counts. Fields that carry no signal are omitted, so anything present is worth reading.agent edits, plan returns a schema-validated plan you approve before anything is written, ask is read-only Q&A, and review runs Codex's own reviewer over uncommitted work, a base branch, or a single commit.resumeThreadId, and get told if the context didn't actually carry over.cancel returns once the process has ended, not once the kill was requested.doctor tool that tells you exactly what's missing if setup isn't right.The caveats are documented rather than buried: what an empty warnings does not prove, and when result is salvage instead of an answer, are in the delegate reference.
You need Node.js 20+ and the OpenAI Codex CLI, already logged in (codex login).
Then just ask:
Delegate to Codex: migrate src/api from callbacks to async/await and update the tests, then walk me through what changed.
That's the whole loop β Claude writes the brief, Codex grinds through the files, Claude walks you through the diff.
Add an MCP server in Cursor Settings β MCP (or project .cursor/mcp.json):
Then ask Cursor to delegate implementation to Codex the same way.
.vscode/mcp.jsonOr run Chat: Install Plugin From Source with this repository's URL.
Under Settings β Tools β AI Assistant β Model Context Protocol (MCP), add a server with command npx and arguments -y codex-delegate-mcp.
~/.codeium/windsurf/mcp_config.jsonHeads-up: Cascade caps you at 100 tools across all servers.
%USERPROFILE%\.mcp.jsonRequires 17.14+. Note the top-level key is servers, not mcpServers.
Add the following server to the client's MCP config:
MIT Β© Andrei Lungeanu
Configuration Β· Security Β· Privacy Β· Terms Β· Changelog
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/codex-delegate)<a href="https://allmcps.com/mcp/codex-delegate"><img src="https://allmcps.com/api/badge/codex-delegate?style=directory" alt="Codex Delegate on AllMCPs" /></a>