browser-bridge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@browser-bridgeOpen Google, search for 'browser automation', and click the first result"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Browser Bridge
AI ↔ Browser Control Bridge: Turn your browser into an MCP toolset. Any MCP client (AI program) calls tools like browser_snapshot / browser_click / browser_type through the standard MCP protocol to operate web pages in a real browser.
Supports any MCP client: Claude, codex, custom agents, curl
Default follow mode: AI automatically controls your currently active tab, zero configuration
Real browser, not headless: login state, CAPTCHAs (prompts you to solve manually), natural anti-scraping characteristics
Quick Start
1. Download
Download one archive from Releases:
browser-bridge-<platform>-<arch>.zip— choose based on your machine's platform
Extract to any directory (referred to as <DIR> below). The directory contains browser-bridge/ (extension), browser-bridge-host, install-host.sh (install-host.ps1 on Windows).
2. Load the Extension
Open
chrome://extensionsTurn on Developer mode in the top-right corner
Click "Load unpacked" and select the extracted
browser-bridge/directory
3. Install the Host
macOS / Linux:
cd <DIR>
./install-host.sh # Windows(PowerShell): .\install-host.ps1After running, it will list detected browsers. Press Enter to install to all, or enter a number to select a specific browser; you can also specify directly with arguments:
./install-host.sh --all # 安装到全部浏览器
./install-host.sh --chrome # 只装 Chrome(--chromium / --edge 同理)The extension ID is built in and fixed, no need to fill it in manually; if your extension ID differs, you can pass it as an additional argument: ./install-host.sh <your-extension-ID>.
If the browser is already open, fully quit and restart the browser after installation.
4. Usage
Connect with any MCP client:
MCP server: http://127.0.0.1:1234/mcpIf the port is occupied, it automatically increments by +1. The actual port is shown in the extension popup (Connected · MCP port xxxx) or in ~/.browser-bridge/port.
codex configuration example (~/.codex/config.toml):
[mcp_servers.browser]
url = "http://127.0.0.1:1234/mcp"After that, just tell the AI "take a look at this page..." and you're done.
Related MCP server: BrowserPilot
MCP Tools
Tool | Parameters | Description |
| — | Query control target and connection status |
| — | List all tabs |
|
| Pin/switch control target |
|
| Create a new tab and navigate immediately (blank page if omitted) |
|
| Close a tab (closes controlled tab by default, auto-returns to follow) |
|
| Activate a tab for the user to see, without changing the control target |
|
| Duplicate a tab (duplicates controlled tab by default) |
|
| Pin/unpin a tab |
| — | Interactive element snapshot (ref number + coordinates) |
| — | Viewport screenshot (dataUrl, for visual understanding of complex layouts) |
| — | Query current controlled page URL and title (lightweight) |
|
| Click |
|
| Double-click |
|
| Type input (compatible with React controlled inputs) |
|
| Batch fill multiple fields |
|
| Key press (supports ctrl/shift/alt/meta) |
|
| Dropdown |
|
| Scroll |
|
| Hover |
|
| Highlight element for 1s (user-visible AI operation location) |
|
| HTML5 drag-and-drop |
|
| Navigation |
|
| Wait for page to stabilize |
AI orchestrates on its own: snapshot → decide → act → snapshot again, until the task is complete.
Control Modes
Follow mode (default): controls your currently active tab; switching tabs switches the target
Pinned mode: locks a specific tab (switching doesn't follow); pin/unpin with one click in the popup, or via AI calling
browser_use_tab
Toolbar icon badge: none = following; AI amber = pinned; ! red = connection error.
Architecture
任意 MCP 客户端
│ MCP (Streamable HTTP, 127.0.0.1:1234/mcp)
browser-bridge host(单进程 = MCP ↔ 帧协议翻译器)
│ native messaging(stdin/stdout 帧)
Chrome 扩展
├─ background:转发、目标解析、保活、状态徽标
└─ content script:快照 / 执行MV3 extensions cannot listen on ports, so the native host is the only channel (same architecture as Chrome's official DevTools MCP).
Building from Source (Developers)
Requires bun:
bun install
bun run build # 当前平台 host + 扩展
./scripts/install-host.sh # 注册 host(默认内置扩展 ID)
bun run scripts/build.ts --all # 交叉编译全部平台 + 发布包(发布用)
bun test # 单元 + MCP API 集成测试(无需浏览器)Configuration
BROWSER_BRIDGE_PORT: MCP initial port (default 1234, auto-increments by +1 if occupied)BROWSER_BRIDGE_MOCK=1: mock extension responses (for development testing)
Troubleshooting
Symptom | Cause | Solution |
Popup shows "host not connected" | Host not installed / browser not restarted | Run install-host, fully quit the browser and reopen |
| Host name contains hyphens (old version) | Update to the new version (host name |
Extension ID mismatch | Loaded with an old manifest | Re-download the extension, or pass |
MCP cannot connect | Host not running | Open the browser + extension first (host is launched by Chrome) |
Target tab unreachable | Page not ready / not http(s) | Wait for the page to load, or pin with |
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityAmaintenanceEnables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.332655MIT
- FlicenseNot gradedqualityDmaintenanceEnables 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.2
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks such as navigation, typing, clicking, and taking screenshots.
- FlicenseNot gradedqualityCmaintenanceEnables browser automation through the MCP protocol, allowing AI agents to control a real browser using accessibility snapshots and natural language commands.
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Stealth web browser for agents: search, fetch, click and type through persistent sessions over MCP.
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
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/weaming/mcp-browser-bridge-extension'
If you have feedback or need assistance with the MCP directory API, please join our Discord server