Chromium Bridge

Name: Chromium Bridge
Author: dashi96

by dashi96version 0.5.3i★ –iRuns on your computer

Registry nameio.github.dashi96/chromium-bridge

Install

Overview

Description from the maker (original English)

MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "chromium-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "chromium-bridge"
      ]
    }
  }
}

Run this in your terminal

claude mcp add chromium-bridge -- npx -y chromium-bridge

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chromium-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "chromium-bridge"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chromium-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "chromium-bridge"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dashi96, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 1379 servers in this category
Published to the registry more recently than 18% of the other 1379 servers in this category
Basic checks equal to or better than 100% of the other 1379 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chromium Bridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.3) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 18 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Chromium Bridge

Русская версия

A bridge between your Chromium-based browser and Claude Code. The official "Claude in Chrome" extension connects in some Chromium browsers (Arc, Vivaldi, and others) but automation hangs: its tools are built on the tab groups API, which is missing or broken there. This bridge uses only plain chrome.tabs / chrome.scripting / chrome.debugger, so it works in any Chromium browser that can load an extension.

Demo

Claude driving the browser through the bridge — opening Wikipedia, typing a search, and landing on the article:

Architecture

Claude Code ⇄ (stdio MCP) ⇄ server/index.mjs ⇄ (WebSocket, 127.0.0.1:8929) ⇄ extension in the browser

⇅ (WebSocket /chat) chat panel (popup on the extension icon)

extension/ — an MV3 extension: the service worker keeps a WebSocket to the local server and executes its commands (tabs, navigation, page text, screenshots, clicks, form filling). Clicking the icon opens the chat panel (chat.html) — a popup anchored to the extension icon.
server/ — an MCP server (stdio) that exposes the browser_* tools to Claude Code and proxies them to the extension. It accepts WS connections only from a chrome-extension://… Origin — regular web pages cannot connect. It also serves the /chat channel: panel messages run through the Claude Agent SDK (authenticated via the Claude Code login) with the same browser_* tools; built-in tools (Bash, Read, etc.) are disabled.

Chat panel

An equivalent of the "Claude in Chrome" side panel: a popup that opens when you click the extension icon (no chrome.sidePanel — it is not supported everywhere). The chat can see the browser: list tabs, read pages, take screenshots, and click.

The panel UI is in English by default and switches to Russian automatically when the browser UI language is Russian. A language selector (Auto / English / Русский) in the bottom bar overrides auto-detection; the on-page badge follows the same choice.

The popup closes when it loses focus (clicking the page) — that is browser behavior. The conversation context is not lost: the panel remembers the session_id and the server resumes the conversation via the Agent SDK resume. A turn that is in flight when the popup closes is interrupted.
It only works while the server is running (usually an active Claude Code session with the chromium-bridge MCP); otherwise the panel shows "Server unavailable".
Model picker in the panel header: "Default" takes the model from ~/.claude/settings.json (whatever was set via /model; SDK sessions do not read Claude Code settings themselves, the server passes the model explicitly), the other entries are hard overrides. Switching applies on the fly (setModel) and is remembered. Startup override: CHROMIUM_BRIDGE_CHAT_MODEL=sonnet in the server environment. Port: CHROMIUM_BRIDGE_PORT (8929 by default) — server side only; the extension always connects to 8929, so changing the port also means editing WS_URL in extension/sw.js and extension/chat.js.
Chat history: the 🕓 button in the header lists past conversations (stored in the panel's localStorage, the last 30).
After each turn there is a usage line: turn tokens (↑ input incl. cache / ↓ output) and the accumulated session cost in $ (on a subscription this is an estimate, not a separate bill).
Screenshots the agent takes along the way are shown right in the chat feed (click to expand). They are not saved to history (localStorage is finite).
You can paste images from the clipboard (Cmd+V in the input, up to 5 per message) — the model sees them; only a marker remains in history.
"Ask before acting" mode (checkbox above the input): reading (tabs, text, screenshots, console, network) proceeds without questions, while mutating actions — clicks/typing/navigation/JS/forms/closing tabs/file uploads — wait for an Allow / Deny card. The agent sees a denial and continues the conversation. Toggling applies immediately, without recreating the session (via the Agent SDK's canUseTool).

On-page indication

When Claude acts on a tab (from the panel or from Claude Code):

an orange glow burns around the page edges with a "✳ Claude is working…" badge, fading 2.5s after the last action;
a virtual cursor (an orange arrow) glides to the action point and pulses a ring on click; it disappears after 3.5s of inactivity.

Both are hidden on screenshots so they don't end up in the frame and confuse the model when working with coordinates. On pages where scripts cannot be injected (chrome:// and the like) the indication is silently skipped.

Installation

Extension: clone this repository, open chrome://extensions (in the right space/profile!), enable "Developer mode", click "Load unpacked", and pick the extension/ folder.
MCP server — either way:

via npm: claude mcp add -s user chromium-bridge -- npx chromium-bridge
from the clone: cd server && npm install, then claude mcp add -s user chromium-bridge -- node "$(pwd)/index.mjs".

It loads at session start — restart your Claude Code session after installing the extension.

For other MCP clients, add this to your config:

"mcpServers": { "chromium-bridge": { "command": "npx", "args": ["chromium-bridge"] } } }

3. Check: the `browser_status` tool should return `{"connected": true}`.

Tools

_As of v0.5._

Tool	What it does
`browser_status`	Check the connection to the extension
`browser_tabs_list`	List tabs (id, title, URL)
`browser_tab_create` / `browser_tab_close`	Open / close a tab
`browser_navigate`	Navigate to a URL; `back`/`forward` for history
`browser_page_text`	Page title, URL, and visible text
`browser_computer`	Mouse/keyboard/screenshots via CDP: clicks by coordinates or ref, drag, hover, type, key combos, scroll, zoomed region screenshot, wait
`browser_read_page`	Accessibility tree with ref ids (filter=interactive)
`browser_find`	Find elements by text/role, returns refs
`browser_form_input`	Set input/textarea/select/checkbox/contenteditable value by selector or ref
`browser_click`	DOM click by CSS selector (plain .click())
`browser_upload_file`	Put files into an
`browser_javascript`	Run JS on the page (await supported)
`browser_console_messages`	Tab console (with a regex filter)
`browser_network_requests`	Tab network requests (with a regex filter)
`browser_resize_window`	Window size
`browser_gif_start` / `browser_gif_stop`	Record a GIF of the tab → file; on long recordings the frame rate halves automatically, so the whole scenario fits

Everything except basic tab operations works through chrome.debugger (CDP): screenshots don't require activating the tab, clicks are real mouse events, and console/network are collected from the first CDP touch of the tab.

Limitations

The extension lives in one browser profile — install it in the one you want to automate.
While the server is running, its periodic ping keeps the extension's service worker awake. If the worker is asleep anyway (e.g. the server has just started), a keepalive alarm wakes it within ~30 seconds, and the server waits up to 12 seconds for reconnection before erroring.
Trust model: the WS server listens on 127.0.0.1 and rejects connections whose Origin is not chrome-extension://…, which keeps web pages out. It does not distinguish between extensions, and a non-browser local process can fake the Origin header — anything running as your user is trusted, like with most local dev tools. Don't run the bridge on a shared machine.
On the first CDP action the browser shows a "Chromium Bridge started debugging this browser" bar — that's normal, the debugger is the control mechanism. Closing the bar detaches the debugger (the next action re-attaches it).
Console/network are not recorded retroactively — only after the tab is first touched.
Port 8929 is owned by one session: a second parallel Claude Code session cannot start its own WS server (the extension stays with the first one).

License

MIT

Chromium Bridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

Chromium Bridge

Demo

Architecture

Chat panel

On-page indication

Installation

Tools

Limitations

License