t3-brave-mcp
Controls tabs in your existing signed-in Brave browser profile through a per-tab chrome.debugger bridge, letting agents open and close allowlisted background tabs (preserving live sessions across OAuth redirects), attach to a live tab on demand, and drive it with Playwright-style actions such as snapshot, click, type, evaluate, and take screenshot.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
t3-brave-mcp
A lightweight, security-scoped Brave / Chromium MCP bridge that lets AI coding agents (Claude Code, Codex, Antigravity, or any stdio MCP client) control tabs in your existing signed-in browser profile — without launching Chrome with a wide-open --remote-debugging-port and without exporting cookies.
Why this exists
Most browser-agent integrations force a bad trade-off:
Isolated browser profiles: you're logged out of every site and constantly blocked by 2FA, OAuth, and CAPTCHAs.
Global
--remote-debugging-port: exposes every tab and session in your personal browser to any local process.
t3-brave-mcp takes a hybrid, per-tab approach using Chrome's chrome.debugger API behind an authenticated loopback WebSocket bridge:
Hands-free allowlisted auto-open (
browser_open_tab/browser_close_tab): Configure trusted domains in the extension popup (e.g.*.example.com). Agents can quietly open background tabs on allowlisted sites using your live sessions, stay attached across OAuth redirects, and close only tabs they opened.One-click / hotkey live tab handoff (
⌥⇧T/Alt+Shift+T): Halfway through a random one-off form or portal you don't want to whitelist? PressAlt+Shift+T(or click Hand off in the popup) to attach the agent to your exact live DOM state, then click×when done.Multi-agent CDP multiplexing: Multiple parallel agents can share the bridge concurrently — each MCP session pins its own
targetIdin memory (no shared-file tab clobbering) and shares cachedRuntime.executionContextCreatedevents without resetting peer sessions.Strict local security model: Authenticated
127.0.0.1loopback bridge (Bearertoken), strictchrome-extension://origin verification on/extension, webpage-origin rejection, per-tabchrome.debuggerscoping, and zero cookie extraction.
Related MCP server: Umbra MCP Server
Architecture
MCP Client (Claude / Codex / Antigravity)
└── stdio MCP (mcp.mjs) ── per-session targetId pin + Playwright MCP
└── Authenticated Loopback Bridge (bridge.mjs + cdp-relay.mjs, 127.0.0.1:9334)
└── MV3 Extension (extension/worker.js) ── per-tab chrome.debugger
└── Explicitly handed-off or allowlist-opened Brave tabsQuick Start
Requires Node.js 22+.
git clone https://github.com/devang-a/t3-brave-mcp.git
cd t3-brave-mcp
npm ci1. Start the local bridge (or install macOS LaunchAgent)
Run in the foreground:
npm startOr on macOS, install the background LaunchAgent (local.t3-brave-mcp.bridge, auto-starts at login):
node scripts/install-service.mjs install
node scripts/install-service.mjs statusFirst run creates a 256-bit local pairing token at ~/.t3/brave-bridge/token.
2. Load the MV3 extension in Brave (or Chrome)
Open
brave://extensionsand enable Developer mode.Click Load unpacked and select this repo's
extension/folder.Open the T3 Brave Bridge popup, click the gear icon, paste the token from
~/.t3/brave-bridge/token, and click Save.Add any domains you want hands-free auto-open for under Allowed sites (or optionally seed them via
~/.t3/brave-bridge/allowlist.json, e.g.["*.example.com"]).
3. Register the MCP server with your agent client
Claude Code:
claude mcp add --scope user brave -- node /absolute/path/to/t3-brave-mcp/mcp.mjsCodex:
codex mcp add brave -- node /absolute/path/to/t3-brave-mcp/mcp.mjsAntigravity / generic MCP
mcp_config.json:{ "mcpServers": { "brave": { "command": "node", "args": ["/absolute/path/to/t3-brave-mcp/mcp.mjs"] } } }
Restart your agent session so the new brave tools appear.
Exposed MCP Tools
browser_backend: Report/selectbravevspreviewmode, checkextensionConnected, view the activeallowlistand attachedtargetIds, and pin atargetIdfor the current session.browser_open_tab: Open (or reuse) an allowlistedhttp(s)URL in Brave (background by default), attach it, and pin itstargetIdfor this session.browser_close_tab: Close an agent-opened tab (refuses to close user-opened personal tabs).Standard Playwright MCP
browser_*tools (browser_snapshot,browser_click,browser_type,browser_evaluate,browser_take_screenshot, etc.), excluding destructive browser-level actions (browser_close,browser_install,browser_run_code).
State & Logs
Runtime state stays outside the repo in ~/.t3/brave-bridge/:
token: local pairing secret (0600)config.json: loopback endpoint + token (0600)selection.json:brave/previewbackend preferenceallowlist.json(optional): JSON array of domain patterns to seed on first connectbridge.log/bridge-error.log: timestamped lifecycle logs (never logs tokens)
Testing
npm test # Unit tests for bridge, auth/origin guards, multiplexing, backend & service
npm run test:brave # End-to-end smoke test in a disposable Brave profileLicense
MIT — see LICENSE. cdp-relay.mjs is adapted from T3 Code's MIT-licensed CdpRelay.ts; see THIRD_PARTY_NOTICES.md.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Let AI agents use your real, signed-in Chrome: tabs, clicks, forms, screenshots and video.
Let AI agents observe and control Chrome tabs you explicitly share via Browse Bridge.
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to securely control a user's existing signed-in Chrome browser through isolated tab groups, with strict per-session ownership and no cookie or token exposure.-
- FlicenseBqualityBmaintenanceEnables AI agents to control existing Chrome and Firefox browser sessions locally, including tab management, navigation, form filling, screenshots, and persistent scripts, without remote relays or debugging ports.36-
- AlicenseNot gradedqualityAmaintenanceLets AI coding tools drive the user's already-signed-in Chrome browser — reading and snapshotting pages, clicking, typing, uploading files, screenshotting, and inspecting tabs, cookies, console, and network traffic. It works through a local Chrome extension bridge, so no remote debugging port is opened and the real, authenticated browser session is used.1 npmISC