# @browserops/bridge [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/quaylabshq/browserops  
**GitHub Stars:** 7  
**npm Downloads (last month):** 192  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/browserops-bridge

## Description
MCP stdio server + WebSocket primary for browserops — drives the browserops Chrome extension. Install `browserops` for the user-facing CLI.

## Tools
Capabilities this server exposes over MCP:

- **browser_screenshot**
- **INTERNAL**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "bridge": {
    "command": "npx",
    "args": ["-y","browserops"]
  }
}
```

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/browserops-bridge/readme_