frsorrentino/chrome-bridge

> By frsorrentino · npm chrome-bridge-mcp · not affiliated with other projects named "chrome-bridge".
**Claude Code borrows a tab from the Chrome you are already using — signed in,
with your extensions and your cookies — works in it, and hands it back. What
only a person can do (a login, a 2FA code, a CAPTCHA, a choice) comes back to
you through handoff: a banner in the page, you act, the agent continues.**
Measured against the official browser extension (paired runs, 29/09/2026, n=5
per task, same model): filling a form, 4.7× fewer turns and 2.8× lower cost;
finding one row in a 1,500-row table, 2.3× fewer turns and 3.4× lower cost;
debugging a broken page, 9.3× fewer turns and 4.3× lower cost. 15 correct
answers out of 15, against 12 (bench/RESULTS.md). ~3× the toolset and no paid plan. 60
web-development tools (navigation, DOM inspection, visual regression, audits,
network mocking) over a local WebSocket bridge, plus a headless instance for
CI. Self-hosted, local-only. Works on ChromeOS.
Quickstart
**Requires** Node.js 18+ and Chrome 135+.
1. Open chrome://extensions, enable **Developer mode**, click **Load
unpacked**, select the extension/ folder.
2. Restart Claude Code.
Then ask for something like *"open localhost:3000, run an accessibility audit
and find the Sign Up button"*: Claude Code calls navigate,
audit and find_text. Because navigate already returns
element refs, click(ref="n1") follows with no discovery turn in between.
> **On ChromeOS/Crostini** install from the Chrome Web
> Store
> instead: an unpacked extension is dropped on every reboot, because the
> container isn't mounted when Chrome starts.
> **On Windows** install.sh does not run from PowerShell or cmd. Use the
> plugin path below (claude plugin marketplace add frsorrentino/chrome-bridge,
> then claude plugin install chrome-bridge@chrome-bridge) with the extension
> from the Web Store, or run install.sh from Git Bash. The plugin's error
> log hooks run in Git Bash, as Claude Code runs every hook, and need Python
> 3.8+ as python3, python or py (the Microsoft Store python3 alias is
> skipped); without Python they stay silent and the tools work the same. For
> launch mode see CHROME_BRIDGE_BROWSER below: Google Chrome cannot load the
> extension there, Microsoft Edge can.
install.sh registers the MCP server with --scope user. To do it by hand:
claude mcp add --scope user chrome-bridge node /path/to/server/index.js.
For execute_js, enable **Allow user scripts** in chrome://extensions →
Chrome Bridge → Details (on Chrome 135-137, enable Developer Mode instead).
**As a plugin, without a clone:** inside a Claude Code session,
/plugin install chrome-bridge --marketplace frsorrentino/chrome-bridge
(one command, Claude Code 2.1.275+; on older versions /plugin marketplace add
frsorrentino/chrome-bridge then /plugin install chrome-bridge@chrome-bridge).
From a shell, claude plugin install has no --marketplace option: run
claude plugin marketplace add frsorrentino/chrome-bridge, then
claude plugin install chrome-bridge@chrome-bridge. Either way the plugin
registers the MCP server from npm (all capabilities) together with the recipes
skill; clients that read Agent Plugins 1.0 get the
same from plugin.json + mcp.json. The extension still comes from the Web
Store or extension/. Pick one path: the plugin and install.sh would
register the same server twice, and so would a plugin added from the
Anthropic directory on claude.ai (it reaches
Claude Code as chrome-bridge@synced) next to a marketplace install. In
claude.ai chat the plugin loads only the recipes skill: the tools need Claude
Code, or Cowork running on your computer, where the local MCP server can start.
Your browser, your login
No blank profile, no debugging port, no cloud browser. The extension runs in
your Chrome, so every site you are signed into is already open to the agent:
webmail, the hosting panel, a client's back office, a staging site behind
basic auth. Tabs the agent opens are marked as its own and closed when the
session ends; your tabs stay yours.
When a page asks for something only you can give, the agent does not guess and
never types credentials. handoff shows a banner in the page with what it
needs — "complete the login with your 2FA, then press Done", "click the button
you mean" — waits for you, and continues from where you left it, redirects