Codex Browser Bridge

Expose the ChatGPT desktop app's browser bridge (formerly Codex Desktop) as an MCP server — drive Chrome and Edge from Claude Code and other agents.

LLM Mart 0 views 19 listing impressions

MCP server and CLI for reusing the installed Codex Browser Use (node_repl) and Computer Use (cua_repl) runtimes from Claude Code, Antigravity, Cursor, OpenClaw, Hermes Agent, and shell scripts, with a compatibility Chromium extension adapter (--surface browser).

License: MIT Latest Release CI Coverage

Website · 中文文档 · Native Setup · Upgrading to 3.0

Choose an entry

Entry Runtime Use it for
--surface native-browser Codex node_repl Installed Codex Browser/Chrome plugin JavaScript API (agent.browsers, tab.playwright, tab.dom_cua).
--surface computer Codex cua_repl Installed Computer Use cua API for desktop windows and unified browser targets.
--surface browser Chromium extension pipe Compatibility only: structured codex_* tools for existing 2.x workflows or hosts without native Codex runtimes.

See Native setup for launch discovery, host environment policy, and elicitation approvals. Browser Use and Computer Use have separate MCP registrations and worker state.

Quick Start

Claude Code plugin

claude plugin install codex-browser --marketplace DeliciousBuding/codex-browser-bridge

The plugin registers both native MCP services (codex-browser and codex-computer). Install and configure the native Codex runtimes first; the plugin does not bundle them. If only one runtime is installed on your machine, the other entry failing to start is expected—use a single-entry manual configuration if you only want one.

Manual MCP configuration

npm i -g @delicious233/codex-browser-bridge   # or download a release binary
{
  "mcpServers": {
    "codex-browser": {
      "command": "codex-browser-bridge",
      "args": ["--surface", "native-browser", "--mode", "mcp"]
    },
    "codex-computer": {
      "command": "codex-browser-bridge",
      "args": ["--surface", "computer", "--mode", "mcp"]
    }
  }
}

Use only the entry you need if a client needs one service or if only one runtime is installed. Client templates are in examples/.

CLI

codex-browser-bridge --surface native-browser --mode doctor
codex-browser-bridge --surface computer --mode doctor
codex-browser-bridge --surface computer call js '{"code":"await cua.listWindows();"}'

Use batch for several native JS calls that share one worker. Use --surface browser explicitly for an existing codex_* script; bare CLI invocations without --surface keep --surface browser as their default for backwards compatibility.

Requires: the configured native runtime for each native entry · Node.js 18+ for the npm/npx path.

Upgrading

From the project's README.

Related servers

Let LLM help you achieve your regression analysis with Stata

21 views

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

21 views

vSphere with Tanzu (VKS): Namespace and TanzuKubernetesCluster lifecycle. Requires vSphere 8.x+.

20 views

Durable agentic memory, encrypted at rest. Fully offline: no network, no API key, no cloud.

19 views