Codex Bridge MCP
Codex Bridge sends questions and file analysis from Claude Code, Cursor and VS Code to the official Codex CLI via Python MCP.
- 120 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Code and questions are sent to Codex CLI and then to OpenAI under your login.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/elyin-codex-bridgeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Code and questions are sent to Codex CLI and then to OpenAI under your login.
This is third-party code. Review the repository files before installing.
What it does
Codex Bridge, a Python MCP server, calls your installed and signed-in Codex CLI and returns the answer to your assistant's chat. Three tools are available: `consult_codex` for a plain question, `consult_codex_with_stdin` for content analysis and `consult_codex_batch` for a set of queries. The server keeps no sessions or cache and uses a 90-second default timeout, changed with `CODEX_TIMEOUT`. Because Codex expects a trusted directory, work outside a git repo needs `CODEX_SKIP_GIT_CHECK`.
Who it is for. Developers on Claude Code or Cursor who want a second opinion from Codex on code without switching tools.
Good fit when
- An independent code review from another model is wanted right from the current chat.
- A large file goes to Codex through stdin instead of pasting it into the query.
- Several project questions go out as a batch and the answers are read together.
- One MCP server is attached to Cursor, Windsurf and Cline at once.
Not a fit when
- Codex CLI is not installed or signed in: the bridge does not authenticate.
- Code must not be sent to OpenAI: queries go to Codex.
- You need sessions and memory across calls: every call is independent.
Example request
Ask Codex through the bridge to review `src/auth.py` and list the three main risks.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
CODEX_TIMEOUTCODEX_SKIP_GIT_CHECK
Limitations
It works only on top of your own Codex CLI and its login, and all queries and file contents go to Codex and then to OpenAI. The bridge is sessionless: context from earlier questions is not kept. Subscription and usage limits follow OpenAI terms. The tool depends on the Codex CLI version and its behavior in untrusted directories, and long queries run into the timeout. The last commit is from October 2026.
How to disable. Run `claude mcp remove codex-bridge` or delete the entry from your client config, then `pip uninstall codex-bridge`. The Codex CLI login stays, so sign out of it separately.
FAQ
Which tools does it expose?
`consult_codex`, `consult_codex_with_stdin` and `consult_codex_batch`. The last takes a list of queries with a separate timeout for each.
What if a query times out?
Raise `CODEX_TIMEOUT` in the config `env` block or split the query. The default is 90 seconds.
Does it work outside a git repo?
Yes, after setting `CODEX_SKIP_GIT_CHECK=true`: by default Codex CLI expects a git repo or a trusted directory.
Is a separate OpenAI key needed?
No, the bridge uses the sign-in of the installed Codex CLI. No separate API billing is needed, but your plan limits apply.
Which clients are covered?
The README gives setups for Claude Code, Cursor, VS Code, Windsurf, Cline, Void, Cherry Studio, Augment, Roo Code and Zencoder.
Discussion
No questions or reviews yet.
Related
MCP serversCodex MCP Tool (cexll)
Codex MCP Tool
An MCP server that sends tasks to Codex CLI from Claude Code and Cursor: code review via @ refs, a sandbox, patch edits, ideas
A Codex skill hands planning and review to ChatGPT over a local MCP bridge and keeps execution and checks in Codex
OpenAI's official plugin: Codex reviews of your changes and task delegation to Codex from inside a Claude Code session
Statusline HUD for Codex CLI inside tmux: context fill, tokens, branch, MCP servers and subagents stay visible in the session.
A Claude Code skill that drives Codex over JSON-RPC: tasks, code reviews, parallel research and messaging between two agents.
Two MCP plugins for Windows: Cursor Bridge serves Cursor index answers to Codex and Claude Code, Grok Build Supervisor runs Grok.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Codex Bridge (this card) | no | not required | 120 | |
| codex-bridge | no | 243 | a different Codex bridge implementation with its own tool set; this one has three calls, including batch and stdin analysis | |
| Codex MCP Server: Codex inside Claude Code | no | API key | 649 | runs Codex as an MCP server; Codex Bridge calls the installed CLI and keeps no sessions |
| Codex Bridge | yes | OAuth | 311 | a separate project with the same name; Codex Bridge is on PyPI and launches through uvx |
README in short
A stateless bridge with minimal dependencies: it needs the `mcp` package version 2 and Codex CLI itself. The README gives configs for about ten clients.