Chromium Bridge

Name: Chromium Bridge
Author: dashi96

作者：dashi96版本 0.5.3i★ –i在你的电脑上运行

注册名称io.github.dashi96/chromium-bridge

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网页与浏览器

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 dashi96 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

星标数多于此分类中其他 1379 个服务器的 0%
发布到注册中心的时间比此分类中其他 1379 个服务器的 18% 更新
基础检查结果等于或优于此分类中其他 1379 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Chromium Bridge 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.5.3）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者：browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT18天前更新

安装

Chrome DevTools MCP

作者：ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.016天前更新

安装

MCP Server Browser

作者：bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“网页与浏览器”中的其他服务器比较i

常见问题

替代选择

Browser Use

Chrome DevTools MCP

MCP Server Browser

作者的 README

Chromium Bridge

Demo

Architecture

Chat panel

On-page indication

Installation

Tools

Limitations

License