Codex Bridge MCP
A local MCP bridge sends chat-client tasks to authorized projects and shows execution and approvals in a workbench.
- 311 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The bridge reads and changes authorized projects and runs commands under access settings; full mode enables writes and network.
Install
- Works in
Manual install
Install the official platform package, start the service and register a test folder. Configure the chosen MCP client, verify the agent connection separately and begin with a read task.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The bridge reads and changes authorized projects and runs commands under access settings; full mode enables writes and network.
This is third-party code. Review the repository files before installing.
What it does
Codex Bridge connects chat clients to authorized projects on a user’s computer. Direct Workspace reads and edits files or runs commands under configured rules. The workbench shows tasks, tool output and approval requests. Delegation can use installed Codex, OpenCode or another supported engine. Engine sign-in is separate from MCP configuration; users choose the project, executor and access mode.
Who it is for. Local development coordinators assigning work from chat and inspecting progress on their own machine.
Good fit when
- A chat task targets a previously authorized local project.
- File operations need a bridge without a separate coding agent.
- Several installed engines should share one task and approval workbench.
- Work needs to resume in an existing executor session.
Not a fit when
- The app must not have full access to a registered project folder.
- Several simultaneous writes to one project must queue automatically.
- You expect the bridge to provide model access itself.
Example request
Connect a test project to Codex Bridge in read-only mode and show the available executor before starting work.MCP
- Transport
- http
- Authentication
- OAuth
Limitations
Registering a folder grants the bridge full access to its contents; begin with a separate test project. Task capabilities depend on engine and permissions: full mode includes writes and network, while read-only mode restricts them. One project permits only one active writing task, and extra tasks do not queue automatically. MCP setup and agent authentication are separate; a connected chat does not prove the executor is ready.
How to disable. Stop tasks, remove project authorization and disconnect MCP. Quit the background app service; closing its Windows window may leave the tray process running.
FAQ
Is Codex required for file operations?
No. Direct Workspace can read and edit authorized files without a separate agent.
Where do I approve a pending action?
Use the local approval card showing the action and the one-time allowance option.
Why was a second write task rejected?
The project’s single active writing slot is occupied; retry after it is free.
Which platforms have packages?
Releases list macOS, Windows and Ubuntu 24.04 packages for their supported architectures.
What should I check after updating?
Restart the app and refresh the client connection so it does not retain stale capabilities.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that gives plain ChatGPT chat a local Codex toolbox: files, commands, Chrome and Edge, live Excel
Codex Control Plane MCP: long Codex Desktop tasks
Codex Control Plane MCP
An MCP server that queues Codex Desktop tasks: the client polls status, approves the plan and reads the final report
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A local bridge linking Claude Code and Codex in one session so the agents message each other and review each other's work
GigaCode Bridge MCP
Gigacode-bridge-mcp
MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review
Codex MCP Server: Codex inside Claude Code
Codex MCP Server
An MCP server that hands tasks to the Codex CLI from inside Claude Code: code questions, change review, web search and resumable sessions
README in short
Projects, configuration and task records stay local. Requests to selected chat and model services still reach those services.