# codex-mcp-bridge [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/buidangminh23/codex-mcp-bridge  
**GitHub Stars:** 27  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/codex-mcp-bridge-2

## Description
Claude ⇄ Codex — Two-way MCP bridge for prompts and replies. Windows, macOS, and Linux.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "codex-mcp-bridge": {
    "command": "npx",
    "args": ["-y","@minhspark/codex-mcp-bridge"],
    "env": {
      "CODEX_BIN": "",
      "CODEX_BRIDGE_DESKTOP_TASKS": "",
      "CODEX_BRIDGE_AUTOSTART": "",
      "CODEX_BRIDGE_THREAD_POLICY": "",
      "CODEX_BRIDGE_ALLOWED_ROOTS": "",
      "CODEX_APP_TOOLS_PIPE_PATH": ""
    }
  }
}
```

**Requires environment variables:** `CODEX_BIN`, `CODEX_BRIDGE_DESKTOP_TASKS`, `CODEX_BRIDGE_AUTOSTART`, `CODEX_BRIDGE_THREAD_POLICY`, `CODEX_BRIDGE_ALLOWED_ROOTS`, `CODEX_APP_TOOLS_PIPE_PATH` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What codex-mcp-bridge MCP server does

The codex-mcp-bridge MCP server connects Claude and Codex so an agent in one application can send work to an active session in the other and receive the response. Conversations remain in their original apps, while the bridge coordinates message delivery for a project directory.

Supported workflows include sending a review from Claude to a Codex task, sending a result from Codex to a Claude Desktop Code session, and creating a new Codex conversation for a feature. Existing work can continue through its original `threadId`. Authorized new Desktop tasks use `delegate_to_codex` or `start_codex_thread` with a fresh `requestId`.

## How it works

The bridge is installed as a local MCP process and registered with Claude Code. Claude Desktop and Claude Code use separate MCP registrations. On Windows and macOS, the native relay connects Codex Desktop to the bridge and forwards the `CODEX_APP_TOOLS_PIPE_PATH` environment variable name through Codex configuration. On Linux and WSL, the documented mode uses a local app-server with the Codex and Claude Code CLIs running under the same Linux user.

Project access is controlled with allowed root directories. Windows separates multiple roots with semicolons; macOS and Linux use colons. A delivery timeout does not necessarily mean that a message was lost: the documented recovery path is to call `wait_codex_reply` with the original `deliveryId` before retrying.

## Setup and configuration

Install the package globally with npm, which requires Node.js 22 or newer:

```bash
npm install -g @minhspark/codex-mcp-bridge@latest
```

macOS and Linux can instead use the provided Homebrew tap. Keep npm and Homebrew as separate installation choices because the first matching command on `PATH` determines which installation is used.

The codex-mcp-bridge MCP server requires signed-in Codex and Claude tooling for the documented desktop and CLI workflows. Configure `CODEX_BIN` with the Codex executable path, set `CODEX_BRIDGE_ALLOWED_ROOTS` to the project directories the bridge may access, and choose the desktop-task and startup behavior appropriate to the platform. The examples also set `CODEX_BRIDGE_THREAD_POLICY=roots`.

Windows and macOS desktop setups use `codex-native-relay-install` and `codex-mcp-bridge-install`. Linux and WSL use the local app-server mode; native Desktop integration is documented only for Windows and macOS. After registration, reconnect the affected MCP servers and test delivery in both directions.

## Tools and capabilities

The documented MCP tools include:

- `codex_bridge_status` for checking the bridge from Claude Code.
- `claude_bridge_status` for checking the Claude side from Codex.
- `native_relay_status` for checking the native relay from Codex Desktop.
- `delegate_to_codex` for sending work to an authorized new Desktop task.
- `start_codex_thread` for creating a Codex conversation.
- `wait_codex_reply` for retrieving a reply after a delivery timeout or delayed response.

The package also includes a ChatGPT connector that can pair a selected Windows or macOS project after the package and native relay are installed.

## Limitations and notes

The codex-mcp-bridge MCP server does not treat registration as proof of successful delivery; verification requires sending a short message and confirming the response in both applications. Claude Desktop and Claude Code registrations must be configured separately. WSL and Windows use different paths and registrations.

For retries, retain the original `requestId` when starting an authorized new Desktop task and use the original `deliveryId` when waiting for a pending reply. Native Desktop integration is not documented for Linux or WSL. The README excerpt does not specify a software license.

_Full upstream README: https://allmcps.com/mcp/codex-mcp-bridge-2/readme_