Chromium Bridge
by dashi96communityv0.5.3
5
An MCP server that connects Claude Code to a Chromium browser extension over local WebSocket, allowing Claude to inspect and control browser tabs, pages, screenshots, input, and navigation. It works around broken tab-groups APIs in some Chromium browsers by using `chrome.tabs`, `chrome.scripting`, and `chrome.debugger` instead.
From the registry: MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation
Install & configure
Prerequisites
- requiredLoad the Chromium extensionClone the repository, open chrome://extensions in the Chromium profile you want to automate, enable Developer mode, click Load unpacked, and select the extension/ folder.
- optionalRestart Claude Code session after installing the extensionThe MCP server loads at session start, so restart your Claude Code session after installing the extension.
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `chromium-bridge` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Load the Chromium extension** — Clone the repository, open chrome://extensions in the Chromium profile you want to automate, enable Developer mode, click Load unpacked, and select the extension/ folder.
Optional prerequisites:
- Restart Claude Code session after installing the extension — The MCP server loads at session start, so restart your Claude Code session after installing the extension.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["chromium-bridge"]
- optional environment variables:
- `CHROMIUM_BRIDGE_CHAT_MODEL`: Startup override for the chat panel model selection. (example: `<model-name>`)
- `CHROMIUM_BRIDGE_PORT`: Port for the local WebSocket server. Default is 8929. If changed, the extension source must also be edited to use the same port. (example: `<port>`)
Note: The extension must be installed in the target Chromium-based browser profile and connected for the server to function. Default local bridge port is 8929. Verify setup with the browser_status tool, which should return connected=true.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: The extension must be installed in the target Chromium-based browser profile and connected for the server to function. Default local bridge port is 8929. Verify setup with the browser_status tool, which should return connected=true.
Tools (18)
browser_status
Check the connection to the extension
browser_tabs_list
List tabs with id, title, and URL
browser_tab_create
Open a new tab
browser_tab_close
Close a tab
browser_navigate
Navigate to a URL or go back/forward in history
browser_page_text
Get page title, URL, and visible text
browser_computer
Perform mouse/keyboard/screenshot actions via CDP, including clicks, drag, hover, typing, scrolling, zoomed screenshots, and wait
browser_read_page
Read the accessibility tree with reference ids, optionally filtering to interactive elements
browser_find
Find elements by text or role and return references
browser_form_input
Set values for inputs, textareas, selects, checkboxes, and contenteditable fields by selector or reference
browser_click
Click an element by CSS selector using DOM click()
browser_upload_file
Upload files into a file input element
browser_javascript
Run JavaScript on the page
Environment variables
CHROMIUM_BRIDGE_CHAT_MODELOverrides the default chat model used by the server's chat panelCHROMIUM_BRIDGE_PORTSets the server WebSocket port (default 8929)Packages
chromium-bridge
npmv0.5.3transport: stdio
Details
- Language
- JavaScript
- License
- MIT
- Released
- Jul 19, 2026
- Last commit
- Jul 22, 2026
- Registry name
- io.github.dashi96/chromium-bridge