Browser Bridge

Let an MCP client (Claude Code, Codex, …) operate your real Chrome — your tabs and logins. You approve new sites and risky actions.

Browser Bridge lets any MCP client — Claude Code, Claude Desktop, Codex, or anything that speaks the Model Context Protocol — drive YOUR real Chrome: your tabs, your logged-in sessions, your cookies. No second browser, no CDP debug port, no --remote-debugging flag. Because it operates the browser you're already signed into, an AI agent can do things a fresh headless browser can't: read a page behind your auth, click through an app you're logged into, or inspect what your app stashed in localStorage. That power is also the risk, so Browser Bridge is built around explicit consent: • Approve every site. A new origin triggers a popup prompt — nothing runs on a site you haven't approved. • Confirm high-risk actions. Submit clicks, link navigations, tab close, and every JavaScript evaluation pop an on-page confirmation you must approve. • Read-only credentials. Cookies and web storage can be read (always masked), never written — there is no cookie/storage write API by design. • Authenticated local bridge. The extension talks to a localhost native host authenticated with a per-run secret; nothing is sent to any remote server. HOW IT WORKS This extension is one half of Browser Bridge. It connects, via Chrome native messaging, to a small local host binary you install separately. Your MCP client connects to that host. All communication stays on your machine (localhost). REQUIRES a separate one-time install of the native host binary. See the setup guide: https://github.com/whg517/browser-bridge Open source (project link below). No analytics, no tracking, no remote code.