Codex Browser Bridge, developed by Deliciousbuding, is an MCP server tool built with Pure Rust. Distributed as a single binary, it enables AI agents to interact with a local Codex Desktop and Chrome installation. This program transforms your existing browser setup into an MCP server, allowing any compatible agent to control it. It connects to the established Codex browser named pipe on the machine, communicating via the same JSON-RPC protocol. This bridge is categorized as an MCP server and a tool for browser automation.

What does Codex Browser Bridge connect to?

Codex Browser Bridge connects directly to a local Codex Desktop and Chrome installation. It utilizes the existing Codex browser named pipe on the machine, communicating through the same JSON-RPC protocol already in place. This setup effectively turns your local browser environment into an MCP server. The bridge operates by integrating with your current browser session and authentication, making it a tool for "MCP server" and "scrapers-browser-automation" categories. It relies on the local, trusted environment of your machine.

Core features and tools

The tool exposes 52 MCP tools for browser automation. Capabilities include opening, closing, and switching browser tabs, navigating pages, going back/forward, and waiting for loads. It captures screenshots (viewport PNG) and reads DOM and accessibility trees, including ARIA role and name search. Agents can click, type, and scroll using CSS selectors, coordinates, or accessibility node IDs. It executes arbitrary JavaScript in the page context, uploads files to <input type=file> elements, and handles JavaScript dialogs. Reading and setting browser cookies are supported, along with running allowlisted CDP diagnostics. Self-diagnosis is available via codex_doctor. The MCP resource codex://tabs is also available, alongside prompt templates login and extract-table.

Who is it for?

The audience for Codex Browser Bridge includes developers and users of AI agents, specifically those compatible with MCP. This covers agents like Claude Code, Cursor, OpenClaw, and Hermes Agent, which need to interact with a real, logged-in Chrome browser session. It is designed for scenarios where AI agents must perform actions within a live web environment. Skip this if your AI agent does not require direct control over a local, authenticated Chrome browser instance.

How to get started

No credentials are required. Setup involves configuring the MCP client to connect via the "stdio" transport, with file uploads needing the CODEX_BRIDGE_UPLOAD_BASE environment variable.

Use cases

• Automating browser interactions such as opening specific URLs, taking screenshots, and clicking elements.
• Enabling agents to inspect and interact with live web applications that require a real browser session, including dashboards, logged-in web apps, local development servers, and documentation sites.
• Managing browser state, which includes listing open tabs and reading or setting browser cookies.

Codex Browser Bridge by Deliciousbuding provides a direct link for AI agents to control a local Chrome browser. It offers a rich set of 52 automation tools, making it suitable for agents needing to perform complex web interactions within an authenticated session. The tool's zero-config nature for the bridge itself simplifies its deployment within a trusted local environment.