# Browser Bridge > 🤖 Browser Bridge for Agentic AI Development - browser extension, MCP, and skilled CLI - **Type:** MCP server - **Install:** `agentstack add mcp-koltyakov-browser-bridge` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [koltyakov](https://agentstack.voostack.com/s/koltyakov) - **Installs:** 0 - **Category:** [Web & Browser](https://agentstack.voostack.com/c/web-and-browser) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [koltyakov](https://github.com/koltyakov) - **Source:** https://github.com/koltyakov/browser-bridge ## Install ```sh agentstack add mcp-koltyakov-browser-bridge ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Browser Bridge (BBX) > **Chrome Web Store:** Install `Browser Bridge (BBX)` from the [Chrome Web Store](https://chromewebstore.google.com/detail/browser-bridge/jjjkmmcdkpcgamlopogicbnnhdgebhie). For local or custom builds, use the unpacked install flow in [docs/unpacked-extension.md](https://github.com/koltyakov/browser-bridge/blob/main/docs/unpacked-extension.md). A local bridge between your coding agent and a real Chrome tab. Browser Bridge gives the agent structured access to DOM, styles, layout, console, network, and reversible patches - starting from the actual tab you already have open, with all its real state intact. See [Quickstart](https://github.com/koltyakov/browser-bridge/blob/main/docs/quickstart.md) to get started in another repo, or browse the rest of the guides in [docs/index.md](https://github.com/koltyakov/browser-bridge/blob/main/docs/index.md). ## Supported Agents Managed installs support OpenAI Codex, Claude Code, Cursor, GitHub Copilot, OpenCode, Antigravity, Windsurf, and generic `.agents` layouts for both MCP and CLI skill setup. OpenAI Codex Claude Code Cursor GitHub Copilot .agents OpenCode Antigravity Windsurf Generic agents ## What it's for - Debugging a UI on `localhost`: read DOM, computed styles, layout, console logs, and network state without a screenshot - Verifying a code change actually rendered the expected result in Chrome - Patching the live page to prove a fix visually, then moving it into source and rolling the patch back - Running structured browser checks from any local agent or IDE, not just one AI product ## Why Browser Bridge Most adjacent tools optimize for different goals. [Playwright](https://playwright.dev/) and headless automation stacks are excellent for deterministic tests and CI - but they start from a clean browser context by design. [Claude in Chrome](https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome) is great for integrated Claude workflows, and the [Codex extension](https://chromewebstore.google.com/detail/codex/hehggadaopoacecdllhhajmbjkdcmajg) is a great option if you use Codex, but both are vendor-specific. Generic MCP browser servers offer broad control without the developer-focused depth. Browser Bridge is optimized for the opposite starting point: **inspect the state that already exists** in a real tab - logged-in sessions, feature flags, seeded storage, SPA state - use structured reads to understand it, test a patch in place, then fix the source. It's open-source, agent-agnostic, and scoped to explicit tab sessions rather than ambient browser control. ## Setup 1. Install [Browser Bridge from the Chrome Web Store](https://chromewebstore.google.com/detail/browser-bridge/jjjkmmcdkpcgamlopogicbnnhdgebhie) in Chrome or another Chromium-based browser 2. `npm install -g @browserbridge/bbx` - installs the CLI and native host 3. Run `bbx install` (Chromium on Linux, Chrome elsewhere), or target a specific browser with `bbx install --browser chrome`, `bbx install --browser edge`, `bbx install --browser brave`, `bbx install --browser chromium`, or `bbx install --browser arc` 4. In the extension side panel, install MCP or CLI (skill) for your agent of choice 5. Enable Browser Bridge for the browser window you want to inspect/control with the AI agent 6. Ask your agent to use Browser Bridge via MCP (`BB MCP` or `Browser Bridge MCP`), or invoke the installed Browser Bridge skill in CLI mode (`/browser-bridge`, `browser-bridge`, or the client-specific skill trigger) On Ubuntu, Chromium is commonly installed as a strict snap, and Flatpak Chromium is similarly sandboxed. If native messaging stays disconnected there, use a non-sandboxed Chromium-based browser such as Google Chrome, Brave, or Edge. MCP mode is self-contained: the server exposes tools and startup instructions, so a separate CLI skill is not required for MCP guidance. ## How it works - The extension is scoped to one explicitly enabled Chrome window at a time - no ambient browser access - Requests default to the active tab in that window unless a tab is targeted explicitly - Sessions are tab and origin scoped, auto-refreshed when possible - All patch operations are reversible and session-scoped - Structured DOM/style/layout reads are the primary transport; screenshots are a fallback - Open-ended investigation should start with structured reads on a smaller, lower-cost subagent when the client supports delegation - The native host daemon auto-starts on demand ## Documentation - [Quickstart](https://github.com/koltyakov/browser-bridge/blob/main/docs/quickstart.md) - [Usage scenarios](https://github.com/koltyakov/browser-bridge/blob/main/docs/usage-scenarios.md) - [Manual setup](https://github.com/koltyakov/browser-bridge/blob/main/docs/manual-setup.md) - [Agent permissions](https://github.com/koltyakov/browser-bridge/blob/main/docs/agent-permissions.md) - [CLI guide](https://github.com/koltyakov/browser-bridge/blob/main/docs/cli-guide.md) - [MCP vs CLI](https://github.com/koltyakov/browser-bridge/blob/main/docs/mcp-vs-cli.md) - [Troubleshooting](https://github.com/koltyakov/browser-bridge/blob/main/docs/troubleshooting.md) - [BridgeClient API](https://github.com/koltyakov/browser-bridge/blob/main/docs/api-reference.md) ## Privacy Browser Bridge itself routes extension data locally through the Chrome extension, native host, and the local client you choose to connect. Browser Bridge does not operate a Browser Bridge cloud service. Your connected agent or IDE may still forward tool calls or tool results to remote services under that product's own settings and privacy policy. See [PRIVACY.md](https://github.com/koltyakov/browser-bridge/blob/main/PRIVACY.md) for the Browser Bridge policy. ## License MIT. See [LICENSE](https://github.com/koltyakov/browser-bridge/blob/main/LICENSE). ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [koltyakov](https://github.com/koltyakov) - **Source:** [koltyakov/browser-bridge](https://github.com/koltyakov/browser-bridge) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-koltyakov-browser-bridge - Seller: https://agentstack.voostack.com/s/koltyakov - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.