Reasonix Browser Bridge
Reasonix Browser Bridge
Reasonix 的自动化浏览器插件(开源)—— 通过 MCP 让 Reasonix 直接控制你的浏览器:标签页、Cookie、任意 JavaScript 执行。Chrome / Edge 通用。
┌─────────────┐ stdio / MCP ┌──────────────────┐ WebSocket ┌───────────────┐
│ MCP Client │ ⇄─────────────⇄ │ MCP Server (Node)│ ⇄ 127.0.0.1:8747 ⇄ │ Extension │
│ (Reasonix…) │ └──────────────────┘ │ (MV3) │
└─────────────┘ └───────┬───────┘
│
tabs / cookies /
scripting / debugger (CDP)
▼
BrowserExtension (
extension/): Manifest V3, connects tows://127.0.0.1:8747, auto-reconnects. Install once per browser (Chrome and Edge).MCP Server (
server/): stdio MCP server that bridges to the extension and exposes browser tools.No special flags needed to launch the browser — no
--remote-debugging-port, no native host / registry setup. Install the extension, run the server, done.
Features / Tools
Tool | Description |
| List all connected browsers (chrome / edge) |
| Extension connection status, version, heartbeat |
| List all tabs (optional URL filter) |
| Open a new tab |
| Switch to a tab |
| Close one or more tabs |
| Reload a tab |
| Full cookie access |
| Run arbitrary JavaScript on any page via CDP (bypasses page CSP) |
| Run multiple JS snippets in ONE debugger attach (fewer toolbar flashes) |
| Screenshot a tab (base64 PNG/JPEG, AI can see the page) |
| Trigger / query downloads |
| Read / switch proxy settings (direct / system / fixed / PAC) |
| Clear cache / cookies / history / localStorage ... |
| List all installed extensions (with enabled state) |
| Search browsing history |
| Read bookmark tree |
| System notification |
| List iframes of a tab |
| Read/write the extension's local storage |
Auto-update check: the extension checks GitHub Releases every 12h (and on browser start). When a new version is published you'll get a system notification, an orange ↑ badge on the toolbar icon, and a "Download" button in the popup — no store required (works for Developer-mode installs).
Multi-browser: Chrome and Edge are both supported. Install the extension in each browser you want to control — every instance auto-connects to the bridge. Most tools accept an optional browser parameter ("chrome" / "edge") to target a specific browser; when only one browser is connected it is used automatically, and when several are connected without a browser argument the server tells you to specify one.
Related MCP server: Chrome MCP Server
Install
1. Install the extension (Chrome / Edge — install once per browser)
Open
chrome://extensions(Chrome) oredge://extensions(Edge).Enable Developer mode.
Click Load unpacked / 加载未打包的扩展程序 and select the
extension/folder.Pin it if you like — the icon shows bridge status (green M = connected).
Note: Chrome 137+ blocks the
--load-extensioncommand-line flag on branded builds; the developer-mode UI install above is the supported way. The same extension folder works in both browsers (same extension ID).
2. Start the MCP server
cd server
npm install
npm startYou should see ✅ 插件已连接 / plugin connected once the extension auto-connects.
3. Configure your MCP client
Add to your MCP client config (Reasonix config.toml):
{
"mcpServers": {
"reasonix-browser-bridge": {
"command": "node",
"args": ["/absolute/path/to/server/index.js"]
}
}
}Usage example
Ask your AI:
List my open tabs. Then run
document.titleon tab #123.
It maps to browser_tabs_list and browser_script_execute.
browser_script_execute takes a JS expression (no return keyword; use an IIFE for async):
document.title
({ count: document.querySelectorAll('a').length })
(async () => { const r = await fetch('/api/data').then(r => r.json()); return r; })() // set awaitPromise: trueSecurity
The WebSocket bridge binds to 127.0.0.1 only; the extension only connects to localhost.
No remote access, no native messaging, no registry changes.
The extension requests full permissions (tabs, cookies, scripting, debugger, downloads, proxy, browsingData, management, history, bookmarks, clipboard, notifications, ... +
<all_urls>) — it is designed as Reasonix's automation bridge, so it can do anything the browser can. Install it only if you trust this project.
Project layout
browser-mcp-bridge/
├── extension/ # MV3 browser extension
│ ├── manifest.json
│ ├── background.js # WS bridge + browser gateway
│ ├── popup.* # minimal status popup
│ ├── content.js # page marker (document_start)
│ └── icons/
├── server/ # MCP server (Node)
│ ├── index.js
│ └── package.json
├── README.md
└── LICENSELicense
MIT
This server cannot be installed
Maintenance
Related MCP Servers
- Alicense-qualityAmaintenanceReliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions supportLast updated1,1146MIT
- Alicense-quality-maintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.Last updated
- AlicenseBqualityDmaintenanceMulti-session browser MCP server that gives AI agents up to 15 fully-isolated browsers running in parallel. 36 tools including navigation, extraction, network intercept, stealth, and self-improvement. Each session has its own cookies, storage, and fingerprint so agents never collide.Last updated37595MIT
- Flicense-qualityDmaintenanceEnables AI to control browsers via natural language for web automation, testing, and data scraping. Supports Chrome-based browsers and integrates with any MCP-compatible AI tool.Last updated2
Related MCP Connectors
AI-powered browser automation — navigate, click, fill forms, and extract data from any website.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/liutingqiu/reasonix-browser-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server