Log inSubmit server
Bridge logo

Bridge

by @browserops

Drives an existing, logged-in Chrome session through MCP tools and a local browser extension.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install 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": {
    "browserops-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "browserops"
      ]
    }
  }
}

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

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y browserops

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 13d ago.

Overview

@browserops/bridge connects MCP-compatible agents to a running Chrome session through a local Node bridge and Chrome MV3 extension. Agents call browser_* tools, while the extension uses Chrome tab, scripting, and debugger APIs to control the authenticated browser. Optional procedure tools let agents save and replay reusable flows. Reach for it when browser tasks require an existing login, 2FA, Cloudflare access, or a real user profile rather than headless automation.

Use cases

  • Test a locally running frontend in a real Chrome profile
  • Read or update authenticated web applications
  • Scrape pages that require login or Cloudflare access
  • Replay shared browser procedures across MCP clients
  • Coordinate browser actions with other MCP servers

Key features

  • Controls an existing logged-in Chrome session
  • Exposes browser_* tools over MCP
  • Uses a local stdio shim and WebSocket bridge
  • Supports optional reusable procedure tools
  • Provides browser-side approval and action tracing
  • Works with multiple MCP clients sharing one profile

Tools2

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

Self-reported~7 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 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 13d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · browserops (npm)

Adoption & maintenance

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

GitHub stars7Stargazers on the source repository.
npm downloads192Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed2Callable tools this server registers over MCP.

How Bridge works

What @browserops/bridge does

@browserops/bridge lets MCP clients operate an already-running Chrome browser, including sites where the user is signed in. It is designed for tasks such as testing a frontend, coordinating browser work with other MCP servers, handling social-media chores, and collecting information from authenticated pages.

The browser session remains the one used by the person at the machine. This supports workflows that depend on existing authentication, 2FA, or access through Cloudflare. The bridge is local-first and binds to 127.0.0.1.

How it works

An MCP client sends browser requests to the browser_* tools exposed by the local Node bridge. The bridge forwards those requests over WebSocket to the BrowserOps Chrome extension. The extension then controls Chrome through chrome.tabs, chrome.scripting, and chrome.debugger.

The MCP entry point is a stdio shim named browserops-shim. It can start the long-lived bridge daemon when the first request arrives, allowing multiple MCP clients to share a Chrome profile. The normal daemon address is 127.0.0.1:57321.

Procedure support is an optional experimental feature. When enabled, agents receive tools for finding, reading, saving, deleting, executing, and resuming stored procedures. Procedures are kept under ~/browserops/procedures/shared/ and can be replayed across clients.

Setup and configuration

The supported environment is macOS or Linux, with Windows available through WSL. Install Node.js 20.10 or newer and Chrome 120 or newer.

Install the CLI globally, then initialize it:

Terminal
npm i -g browserops
browserops init

Initialization creates a token at ~/.browserops/token, starts the bridge, prepares the shared procedure directory, and can add the MCP configuration to detected clients. The --yes, --no-mcp, --client, and --dry-run flags control that process. Install the BrowserOps extension from the Chrome Web Store and confirm the connection in its onboarding tab.

The CLI includes commands for starting, stopping, restarting, inspecting status, viewing logs, diagnosing setup, upgrading, and synchronizing client configuration. Manual MCP configuration uses browserops-shim as a stdio command.

Tools and capabilities

The always-available browser tool set is exposed through names beginning with browser_. The extension can work with Chrome tabs, page scripting, and debugger-driven browser control. Procedure tools become available after enabling the feature and restarting the daemon:

  • procedures_search
  • procedures_get
  • procedures_save
  • procedures_delete
  • procedures_execute
  • procedures_resume

Browser-side approval defaults to automatic approval, including JavaScript execution and actions on sensitive domains. Set BROWSEROPS_APPROVAL=gate or enable approval in the extension to require confirmation for risky actions. Set BROWSEROPS_TRACE=1 to write auto-approved actions to the trace file.

Limitations and notes

The bridge requires Chrome and the BrowserOps extension running on the same local environment. It is not a headless browser service; it operates the available Chrome session and its logged-in state.

Certain actions are blocked regardless of approval mode. These include destructive browser shortcuts such as closing or opening windows and tabs, plus navigation to javascript:, file://, and chrome:// URLs.

The procedure feature is disabled by default and must be explicitly enabled. Launcher-side approval is separate from browser-side approval: the CLI may also configure the selected agent launcher to run with reduced prompting unless safe mode is enabled.

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 Bridge

@browserops/bridge is an MCP server that connects AI clients to a running Chrome session through the BrowserOps extension and local Node bridge. Its main tools are the browser_* tools for controlling tabs and pages, plus optional procedure tools for searching, saving, executing, and resuming reusable browser workflows.

Install the CLI with `npm i -g browserops`, run `browserops init`, and install the BrowserOps Chrome extension. Initialization starts the local bridge and can register `browserops-shim` with detected MCP clients.

Yes, @browserops/bridge works with Cursor through the `browserops-shim` stdio command. `browserops init` can add the configuration automatically, or you can register the command in `~/.cursor/mcp.json`.

Set `BROWSEROPS_APPROVAL=gate` when starting the bridge or enable Require approval for risky actions in the extension popup. Browser-side approval is independent of the launcher’s own approval or safe-mode settings.

Run `browserops feature enable procedures` and then `browserops restart`. The daemon will expose the procedure-store tools, including search, get, save, delete, execute, and resume operations.

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 PreviewBridge AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/browserops-bridge?style=directory)](https://allmcps.com/mcp/browserops-bridge)
HTML Embed
<a href="https://allmcps.com/mcp/browserops-bridge"><img src="https://allmcps.com/api/badge/browserops-bridge?style=directory" alt="Bridge on AllMCPs" /></a>