T3rnel Browser — Session Bridge
Official# MCP Session Bridge
[](https://mcpservers.org/servers/t3ratech/mcp-session-bridge)
[](https://glama.ai/mcp/servers/t3ratech/mcp-session-bridge)
A free MCP (Model Context Protocol) server that exposes **authenticated browser-session automation**: `session_*` tools that run in the user's own Chrome profile and real logged-in session, which cloud browser APIs cannot do. A free **standalone** mode is also available; it launches a dedicated automation browser so the same `session_*` tools work without the extension or a license.
## What it does
- Serves MCP over stdio (newline-delimited JSON-RPC) to any client that speaks the Model Context Protocol. The setup guide covers the common ones.
- Uses a dual-transport design:
- **Extension mode (free; the browser-control tools need no account, the extension's own tools need a sign-in and have a monthly allowance, Pro tools are gated by the extension)** — since 1.3.0 the bridge serves a loopback WebSocket the extension's service worker dials out to, so `npx @t3ratech/mcp-session-bridge` is the whole setup: no global install, no `--install`, no native host manifest. The first connection asks once in the extension panel, permanently. The pre-1.3 path — relay socket to a native messaging host Chrome spawns — remains as a fallback for hosts registered by older installs.
- **Standalone mode (free)** — launches its own headful or headless CDP browser on a persistent profile and drives it directly. No license, no extension, and no access to the user's everyday browser.
- Returns structured page context, form values, snapshots, and screenshots without shipping session cookies to a remote browser.
- Works with more than one browser at once. When several browsers carry the extension (Chrome and Brave, say), the first call asks each for its tab list with `browser_list_tabs` and keeps using the first that reports a tab, so a browser that sees no windows cannot capture the session; with one browser connected nothing is probed.
## Price
The bridge itself is free, and this package enforces no licence of its own.
Extension mode reaches the buyer's real authenticated session through the T3rnel Browser
extension, and the Pro tools it exposes are gated by that extension's own Pro tier —
a one-time payment that covers up to five signed-in browsers, priced by WavePay and shown in the extension. Standalone mode is free and needs neither the extension nor a
licence. There is no separate subscription for this package, and nothing here checks for
one; earlier drafts of this file advertised $9/mo and $39/mo tiers that were never
implemented, never enforced and never purchasable.
## Project layout
- `src/server.js` — MCP stdio server: tool surface, schema validation, dual-transport routing, loopback WebSocket endpoint, relay client with reconnect and timeouts, and standalone CDP launcher.
- `src/cdp.js` — standalone CDP browser management and WebSocket client.
- `src/ws-server.js` — the loopback WebSocket endpoint extension mode dials out to (1.3.0+).
- `src/native-host.js` — legacy path: native messaging host spawned by Chrome; owns the relay socket and multiplexes concurrent MCP servers.
- `src/framing.js` — the 4-byte length-prefixed JSON framing shared by native messaging and the relay socket.
- `src/tools.js` — the `session_*` tool definitions, validation, and mapping to the extension's `browser_*` tools.
- `src/license.js` — offline Ed25519 license verification helpers used by the extension and tests.
- `src/install.js` — `--install` / `--uninstall` native host registration for Chrome, Chromium, Brave and Edge (legacy transport only — not needed for 1.3.0+).
- `docs/setup-guide.md` — installing on the common MCP clients, plus verification and troubleshooting.
- `docs/chrome-validation-checklist.md` — end-to-end validation steps for Chrome with the T3rnel Browser extension.
- `ads/` — `ad-copy.md`, the shared headline and description copy used when submitting to MCPize, Smithery, mcp.so and PulseMCP.
- `tests/` — `node --test` suite, including end-to-end tests through a real relay socket and native-messaging framing, plus standalone-mode coverage.
## Browser support
Extension mode needs the T3rnel Browser extension, which is packaged for Chrome, Brave,
Edge, Opera, Chromium and Firefox and ships from each browser's own extension store. Brave
and Chromium install from the Chrome Web Store; Edge, Opera and Firefox each have a
separate package. Opera implements no side-panel API and Firefox no debugger API, so both
are partly supported; the extension's manifest generator states which capabilities are
absent on each. Standalone mode has no browser requirement at all — it launches its own CDP
browser.
The extension exposes 97 browser tools over this bridge — the full surface minus three
licence-maintenance tools that stay panel-only — subject to the extension's own Pro
gating. The count stays under the 100-tool limit some MCP clients enforce, and
`session_install` (setup instructions) and `session_read_url` (a public page as Markdown) bring the bridge's own listing to 99.
An older extension that publishes 100 tools would push the merged list past that limit —
Google Antigravity refuses to install it — so the bridge then leaves `session_md_diff` and
`session_check_spelling` unlisted. They still run when called by name.
## Supported clients
- Claude Code / Claude Cowork
- Cursor
- VS Code
- Windsurf / Devin Desktop
- Google Antigravity
- IntelliJ
- Codex
- Grok Build
- Kimi Code / Kimi Desktop
- JCode
- Cline
- OpenCode
- Continue.dev
- KiloCode
- Roo Code
- Aider
- OpenClaw
- Hermes
- OpenFang
- Any client that speaks MCP stdio
## Questions
### What is the MCP Session Bridge?
It is a free MCP server that lets an AI agent drive the browser you are already signed into: `session_*` tools that run in your own Chrome profile and real logged-in session, which cloud browser APIs cannot do. It serves MCP over stdio to any client that speaks it.
### How do I install it?
Add it to your MCP client with command `npx` and args `-y @t3ratech/mcp-session-bridge`. Since 1.3.0 that is the whole setup: no global install, no `--install`, no native-host manifest. The T3rnel Browser extension finds the bridge on its own over a loopback WebSocket.
### Is it free?
Yes. The bridge is free and this package enforces no licence of its own. Extension mode exposes the T3rnel Browser extension's tools, and the browser-control tools (navigation, reading, clicking, typing, screenshots, network and console capture, uploads) need no account and are never limited. The extension's own tools need a signed-in extension account: a free account gets three uses a month of the free ones, and the Pro tools are gated by that extension's own one-time Pro tier. Standalone mode is free and needs neither the extension nor a licence.
### Does it work without the extension?
Yes. Standalone mode launches its own CDP browser on a persistent profile and drives it directly. It has no access to your everyday browser; extension mode is what reaches your real, signed-in session.
### Is it safe to give an agent my logged-in browser?
The bridge listens on 127.0.0.1 only, so nothing on your network can reach it. Whether the agent must ask before acting is the extension's approval gate: it ships off and can be armed in the extension's Settings so page-changing tools ask first. See the extension's FAQ for the risk class of every tool.
### Which MCP clients does it work with?
Claude Code and Claude Desktop, Cursor, VS Code, Windsurf, Antigravity, IntelliJ, Codex, Grok Build, Kimi Code and Desktop, JCode, Cline, OpenCode, Continue.dev, KiloCode, Roo Code, Aider, OpenClaw, Hermes, OpenFang, and any client that speaks MCP over stdio.
### How many tools does it expose?
The extension exposes 97 browser tools over this bridge, and `session_install` and `session_read_url` bring the bridge's own listing to 99 — under the 100-tool limit some clients enforce.
The tool list is about 15,000 tokens of every session, so a client that only needs the everyday verbs can list fewer: `T3RNEL_SESSION_TOOLS=core` (or `--tools core`) lists the 24 tools that cover navigating, reading, clicking, typing and screenshots, and `--tools core,network,design` adds those profiles (`network`, `design`, `test`, `vault`, `page`). `all` is the default. A tool that is not listed can still be called by name, and an unknown profile name stops the bridge at startup rather than listing nothing.
### Does the snapshot cost many tokens?
With the extension connected, `session_snapshot` returns one short line per element, `- button "Buy" [@e4]`, which on a 231-element page is about 7,600 characters against about 60,600 for the structured form; `format: "json"` returns the structured form with selectors. Refs from either form work in `session_click`, `session_fill`, `session_type`, `session_select` and `session_press`. The standalone browser always returns the structured form.
### Which browsers are supported?
Chrome, Brave, Edge and Chromium fully; Opera (no side-panel API), Firefox (no debugger API) and Safari partly. Standalone mode has no browser requirement.
## Install the T3rnel Browser extension
The bridge works best with the T3rnel Browser extension, which lets your AI drive the browser you are already signed into:
<https://browser.t3ratech.co.zw/>
Every `session_*` error that reports the extension missing — on any tool that genuinely
needs it — carries this link. Standalone-capable tools never nag: they just work
without the extension.
## Where this is listed
- [npm](https://www.npmjs.com/package/@t3ratech/mcp-session-bridge) · [Official MCP registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.t3ratech%2Fmcp-session-bridge/versions/latest) · [Smithery](https://smithery.ai) · [Glama](https://glama.ai/mcp/servers/t3ratech/mcp-session-bridge)
- Agent skills: [skills.sh](https://skills.sh/t3ratech/mcp-session-bridge/signed-in-browser) · [ClawHub](https://clawhub.ai/t3ratech/skills/t3rnel-signed-in-browser)
- Listed in the [Claude Market skill directory](https://www.claudemarket.ai/skills)
## Licence
Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for the full text.
The published npm package is free to use for any purpose, commercial or otherwise. You may
read and modify this source; redistribution is governed by the Apache-2.0 terms.
TDQS
Scored across 22 tools
Each tool has a distinct, well-defined purpose with clear boundaries: navigation, reading, interacting, waiting, recording, and login are all separated. Tools like session_read_page vs session_snapshot and session_fill vs session_type explicitly differentiate their use cases and recommend alternatives, eliminating ambiguity.
All tools follow a strict 'session_' prefix with a verb or verb_noun structure in snake_case, such as session_list_tabs, session_close_tab, session_record_start. The pattern is uniform, making it easy to predict and group related actions.
At 22 tools, the count is slightly above the typical 3-15 range, but each tool addresses a distinct browser automation capability (tab, navigation, interaction, recording, login). The granularity is justified by the breadth of the domain, though it borders on heavy.
The tool surface covers the full lifecycle of browser session automation: setup, health check, tab management, page navigation, reading and interacting (click, fill, type, select, press), waiting, screenshots, login credential storage, and full recording/replay. There are no obvious dead ends; all workflows from basic browsing to complex testing workflows are supported.