A Chrome extension that connects Claude Code to your browser via DevTools Protocol. Click, type, navigate, screenshot — 10 automation commands with trusted input events.
No Puppeteer. No Selenium. No headless browser eating your RAM. browser-bridge-ext talks directly to the tab you already have open through Chrome DevTools Protocol.
Claude Code connects to the extension over a local WebSocket, gets real DOM access, and dispatches trusted input events — the same kind the browser generates when you actually click and type.
Load browser-bridge-ext into Chrome or Brave. It runs quietly in the background, waiting for a connection from the MCP server.
Add claude-browser-bridge to your Claude Code config. The MCP server connects to the extension over WebSocket on localhost:7225.
Ask Claude to interact with any page. It can click elements, fill forms, take screenshots, run JavaScript, and navigate between pages.
The extension uses exponential backoff reconnection with keepalive pings, so the connection stays solid even if the MCP server restarts.
Navigate, click, type, scroll, screenshot, eval JS, get page content, get element info, fill forms, and wait for elements. Everything you need for real browser automation.
Dispatches trusted input events through CDP — the same mechanism Chrome uses internally. Sites can't distinguish these from real user interactions.
The extension connects to the MCP server on localhost:7225. No cloud services, no API keys, no data leaving your machine. Everything stays local.
Exponential backoff reconnection with keepalive pings. If the MCP server restarts or the connection drops, the extension reconnects automatically.
Two pieces: the browser extension and the MCP server.
git clone https://github.com/softwaresoftware-dev/claude-browser-bridge-extension.git
chrome://extensions → Developer mode → Load unpacked
claude mcp add browser-bridge npx claude-browser-bridge
claude "navigate to example.com and take a screenshot"