Log inSubmit server
Chrome Bridge logo

Chrome Bridge

Connects MCP agents to a logged-in Chrome session for web development, audits, testing, navigation, and human handoffs.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Chrome Bridge

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "chrome-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-bridge-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 44 tools correctly (Today).

Overview

chrome-bridge connects an MCP client to the Chrome instance you already use, including its active logins, cookies, and extensions. A local Node.js server communicates with a browser extension over WebSocket and exposes 60 web-development tools for navigation, DOM inspection, audits, screenshots, console output, network mocking, and more. Human-only steps such as 2FA, CAPTCHA completion, and ambiguous page choices return through an in-page handoff banner. Reach for it when an agent needs to work in an authenticated browser, test local sites, or run isolated headless sessions in CI.

Use cases

  • Test authenticated staging sites in an existing Chrome profile
  • Run accessibility, SEO, and security audits on local pages
  • Replay recorded browser flows in headless CI
  • Debug console errors, visual changes, and network requests
  • Hand off 2FA, CAPTCHA, and ambiguous page choices to a person

Key features

  • 60 web-development tools over a local WebSocket bridge
  • Authenticated Chrome sessions with existing cookies and extensions
  • In-page human handoffs for login and verification steps
  • Headless launch mode for isolated sessions and CI
  • Visual regression, audits, console inspection, and network mocking
  • CLI batching plus session recording and replay

Tools44

What Chrome Bridge lets your agent do. Expand a tool for its parameters.

Verified live~12.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 25d

What it can do

From the 44 tools this server returned when we ran it; 44 declare their own safety hints.

Runs commands · 2Can delete or modify data · 6Writes files · 2Handles credentials · 8Makes network requests · 17Read-only tools · 35
Unusual tool instructions. 1 tool description contain text aimed at the AI model rather than at you (reaches for local secrets). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age88 days
Maintainers1

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · chrome-bridge-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads4.4kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed44Callable tools this server registers over MCP.

How Chrome Bridge works

What chrome-bridge does

chrome-bridge gives an MCP client access to a real Chrome session instead of starting with a blank browser profile or requiring a remote browser service. The agent can use sites where you are already signed in, along with the session's cookies and installed extensions. It can open and operate its own tabs while leaving your existing tabs untouched; agent-owned tabs are closed when the session ends.

The toolset is aimed at web development and browser automation. It covers navigation, DOM and text inspection, element interaction, form filling, console checks, accessibility, SEO and security audits, screenshots, visual comparison, and network behavior. Server-side table filtering helps keep large-page responses smaller. A separate CLI can run batch operations through shell tools such as grep and jq without sending every intermediate result through the model.

How it works

The local MCP server connects to the Chrome extension through a local WebSocket bridge. The extension runs inside the Chrome profile you are using, so authentication remains in that browser. When an action requires a person, handoff displays an in-page banner describing the required step. You can complete a login, enter a 2FA code, solve a CAPTCHA, answer a question, or select page elements; the agent then continues from its previous state.

The server also supports launch mode for isolated browser sessions and CI. It can start a dedicated Chromium-based browser with an ephemeral profile, including headless operation. Recording a session with session_record and replaying it with replay supports smoke tests without a model in the loop.

Setup and configuration

The runtime requirements are Node.js 18 or newer and Chrome 135 or newer. The standard setup clones the repository, runs install.sh, loads the extension/ directory as an unpacked extension from chrome://extensions, and restarts Claude Code. The script registers the MCP server for the user scope. Manual registration uses claude mcp add --scope user with the server's index.js path.

The project also provides a Claude Code plugin that installs the npm-based MCP server and its recipes skill. Use either the plugin route or install.sh, not both, because each registers the same server. On ChromeOS with Crostini, install the extension from the Chrome Web Store. On Windows, use the plugin, Git Bash, or a supported browser launch configuration rather than running install.sh from PowerShell or Command Prompt.

For execute_js, enable user scripts in the Chrome Bridge extension settings. In launch mode, CHROME_BRIDGE_BROWSER can select a browser binary. Chromium, Microsoft Edge, Brave, and Chrome for Testing are supported launch choices; Google Chrome 137 and newer does not load the extension in this mode.

Tools and capabilities

  • Navigate pages and return element references for follow-up actions such as clicking.
  • Inspect the DOM, find text, fill multiple form fields, and interact with page elements.
  • Run accessibility, SEO, and security audits with reports written to disk.
  • Read console output, assert selectors and text, and execute JavaScript.
  • Capture screenshots, compare images with screenshot_diff, and inspect visual changes.
  • Stub network responses or add request headers for network testing.
  • Record and replay browser sessions, including headless CI workflows.
  • Pause for human input through an in-page handoff banner.

Limitations and notes

The browser extension must be installed and connected to the local server. ChromeOS requires the Web Store installation because unpacked extensions are removed after reboot. The browser's existing authentication is available to the agent, so use an appropriate Chrome profile and treat access accordingly.

The server is self-hosted and local-only. Launch mode is intended for isolated profiles and CI, while normal operation uses the Chrome profile already open on the computer. Claude Code is the documented client workflow; in claude.ai, the plugin loads its recipes skill, but the browser tools require Claude Code or Cowork running on the computer.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Chrome Bridge

chrome-bridge is an MCP server that connects an MCP client to your logged-in Chrome through a local browser extension and WebSocket bridge. Its main tools cover navigation, DOM inspection, forms, audits, screenshots, console checks, network mocking, JavaScript execution, session replay, and human handoffs for steps such as 2FA or CAPTCHA completion.

Install Node.js 18+, Chrome 135+, the Chrome Bridge extension, and the local server, then register it with Claude Code. The repository setup runs `install.sh`; alternatively, add the server manually with `claude mcp add --scope user`. The Claude Code plugin provides another installation path.

Yes, chrome-bridge operates in the Chrome profile where the extension is installed, so sites you are already signed into are available through that session. It does not type credentials for human-only steps; `handoff` lets you complete login, 2FA, CAPTCHA, or other required actions in the page.

Yes, launch mode starts a dedicated Chromium-based browser with an ephemeral profile and supports headless operation. You can combine `session_record` and `replay` for smoke tests and CI workflows. `CHROME_BRIDGE_BROWSER` selects another browser binary when needed.

Yes, chrome-bridge supports ChromeOS with Crostini. Install the extension from the Chrome Web Store rather than loading it unpacked, because the unpacked extension is removed when the device reboots.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewChrome Bridge AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/chrome-bridge?style=directory)](https://allmcps.com/mcp/chrome-bridge)
HTML Embed
<a href="https://allmcps.com/mcp/chrome-bridge"><img src="https://allmcps.com/api/badge/chrome-bridge?style=directory" alt="Chrome Bridge on AllMCPs" /></a>