MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation
MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. That is what the chromium mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
The server publishes 14 tools. What each one is for:
browser_status — Check the connection to the extensionbrowser_tabs_list — List tabs (id, title, URL)browser_navigate — Navigate to a URL; back/forward for historybrowser_page_text — Page title, URL, and visible textbrowser_computer — Mouse/keyboard/screenshots via CDP: clicks by coordinates or ref, drag, hover, type, key combos, scroll, zoomed region screenshot, waitbrowser_read_page — Accessibility tree with ref ids (filter=interactive)browser_find — Find elements by text/role, returns refsbrowser_form_input — Set input/textarea/select/checkbox/contenteditable value by selector or refbrowser_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)The server ships on npm as chromium-bridge, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Chromium's toolset — browser_status, browser_tabs_list, browser_navigate and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dashi96; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Chromium's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| browser_status | Check the connection to the extension |
| browser_tabs_list | List tabs (id, title, URL) |
| 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 <input type="file"> |
| 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 |
{
"mcpServers": {
"chromium-bridge": {
"command": "npx",
"args": ["chromium-bridge"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.