T3rnel Browser — Session Bridge
OfficialIt is a free MCP server that lets an AI agent automate an authenticated browser session through session_* tools, using either the T3rnel Browser extension or a free standalone CDP browser.
Get setup instructions and diagnose transport/browser health.
List and close tabs, and navigate within the user's logged-in session.
Snapshot interactive elements, read rendered page text, and wait for load/URL/selector conditions.
Click, fill, type, select dropdown options, press keys, and evaluate JavaScript in the page.
Capture viewport screenshots.
Store and fill credentials through the extension's Pro vault.
Record, list, inspect, stop, and replay browser interactions.
Some tools require the T3rnel Browser extension or its Pro tier; standalone mode is free but uses its own browser profile.
Allows automation of the user's authenticated Brave browser session through the T3rnel Browser extension, including structured page context, form values, snapshots, and screenshots.
Partially supports browser automation in Firefox through the T3rnel Browser extension, with limitations due to Firefox lacking a debugger API.
Partially supports browser automation in Opera through the T3rnel Browser extension, with limitations due to Opera lacking a side-panel API.
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-bridgeis 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_tabsand 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.
Related MCP server: byob
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— thesession_*tool definitions, validation, and mapping to the extension'sbrowser_*tools.src/license.js— offline Ed25519 license verification helpers used by the extension and tests.src/install.js—--install/--uninstallnative 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 --testsuite, 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
Listed in the Claude Market skill directory
Licence
Licensed under the Apache License, Version 2.0. See 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.
Available Tools
22 toolssession_clickADestructive
Click an element, by CSS selector or by an @eN ref from session_snapshot. Scrolls the element into view and dispatches a real mouse press and release at its centre, so handlers that ignore synthetic events still fire. Returns {clicked} naming what was targeted. Fails with 'Element not found' rather than clicking something else when nothing matches.
Inputs: selector (required), ref, tabId.
session_close_tabADestructive
Close a tab, named explicitly by its id from session_list_tabs. Returns {closed, tabId}. Unlike every other tool here, tabId is required and there is no active-tab default: closing a tab is not undoable, and the active tab is the one the user is looking at. Requires the T3rnel Browser extension; the standalone browser refuses it by name.
Inputs: tabId (required).
session_evaluateADestructive
Run JavaScript in the page's own context and return its completion value. Use it for what the other tools do not cover — reading computed styles, walking a data structure the page holds, or checking a condition too specific for session_wait. Objects come back as formatted JSON, strings as themselves, and an expression with no value as "undefined". End the code with the expression you want back; a trailing statement returns nothing useful.
Inputs: code (required), tabId.
session_fillAIdempotent
Set a form field's value in one step — input, textarea, or a rich-text editor such as ProseMirror, Lexical or Slate. Writes through the native value setter and then fires input and change, which is what React and Vue listen for. Returns {filled} naming the field. Use session_type instead when a field only reacts to real keystrokes, and session_select for a dropdown.
Inputs: value (required), selector (required), ref, tabId.
session_healthARead-onlyIdempotent
Report which transport is live and what it can do. Call this first when another tool fails unexpectedly: it separates 'the extension is not running' from 'this browser does not implement that API', which produce very different fixes. Returns {ok, mode, browser, profileDir} in standalone mode, and the connection state plus the available browser APIs when the extension is attached.
Inputs: no named parameters.
session_installARead-onlyIdempotent
Return setup instructions for the T3rnel Browser extension and for the free standalone automation browser. Needs no browser and no licence, so it is the one tool that always answers — call it when another tool reports the extension is missing. Returns installation steps as text.
Inputs: no named parameters.
session_list_tabsARead-onlyIdempotent
List every open tab. Returns an array of {id, title, url}. The ids are what every other tool's optional tabId argument accepts; omit tabId and a tool acts on the active tab, which is rarely what you want once you have opened tabs of your own.
Inputs: no named parameters.
session_loginAIdempotent
Decrypt stored credentials for a domain and fill them into the page's sign-in form. Requires the T3rnel Browser extension with Pro, because the encrypted vault lives in the extension; the refusal comes from the extension rather than from this bridge, so there is one gate rather than two that can disagree. The standalone browser has no vault — sign in once by hand in its profile instead, and the session persists.
Inputs: domain (required), tabId, submit, masterPassword.
session_pressADestructive
Press a single keyboard key on the focused element, or on a named element after focusing it. Use it to submit a form with Enter, dismiss a dialog with Escape, or walk a suggestion list with ArrowDown. Returns {pressed} naming the key. Supported keys are Enter, Tab, Escape, Backspace, Delete, ArrowUp, ArrowDown, ArrowLeft, ArrowRight, Home, End, PageUp, PageDown and Space; anything else fails with the supported list rather than doing nothing.
Inputs: key (required), ref, tabId, selector.
session_read_pageARead-onlyIdempotent
Read a page's visible text, as rendered in the user's authenticated session. Returns {url, title, text, truncated}; text is the body's rendered innerText capped at 50,000 characters, and truncated is true when the page was longer. Prefer this over session_snapshot when the goal is to read or summarise; prefer session_snapshot when the goal is to interact.
Inputs: tabId.
session_record_eventsARead-onlyIdempotent
Fetch the captured events of a recording, in the order they happened. Returns {events, count}, where count is the total held for the session and events is one page of {type, timestamp, tabId, data}; type is one of click, scroll, keypress, input, navigation, focus, select or resize. Page through long recordings with limit and offset rather than reading them whole, since a session can hold tens of thousands of events. Requires the T3rnel Browser extension.
Inputs: sessionId (required), limit, offset.
session_record_listARead-onlyIdempotent
List every recording, running or finished, so a caller can find the id that session_record_events and session_record_replay need. Returns {sessions}, each entry being {id, tabId, active, startedAt, stoppedAt, stoppedReason, eventCount, durationMs}. Requires the T3rnel Browser extension.
Inputs: no named parameters.
session_record_replayADestructive
Replay a stopped recording in its original tab, reproducing the recorded interactions in order. Returns {sessionId, totalEvents, replayedEvents, failedEvents, errors}, so a partial replay reports which steps failed instead of appearing to succeed. The tab must still be open. This acts on the live page and its effects are real — it will re-send messages, re-submit forms and re-spend money — so the extension classifies it high risk and gates it behind an approval prompt. Requires the T3rnel Browser extension.
Inputs: sessionId (required), speed.
session_record_startA
Begin recording what happens in a tab: clicks, scrolls, keystrokes, form fills, selections and navigations, each with a timestamp. Returns {recording, sessionId, tabId} — keep the sessionId, since every other recording tool needs it. Requires the T3rnel Browser extension. Recording stops on its own if the tab closes or after four hours.
Inputs: tabId, maxEvents, sessionId.
session_record_stopAIdempotent
Stop a recording and return {recording, sessionId, eventCount, durationMs}. The events themselves are read separately with session_record_events, so this is cheap to call on a long recording. Requires the T3rnel Browser extension. With several recordings active, sessionId is required and the error names how many are running.
Inputs: sessionId.
session_screenshotARead-onlyIdempotent
Capture what is currently on screen in a tab. Returns a data: URL holding a base64 PNG or JPEG. This is the visible viewport only — it does not scroll or stitch, so a long page needs the extension's full-page capture instead.
Inputs: tabId, format, quality, windowId.
session_selectAIdempotent
Choose an option in a dropdown, by value, by visible text, or by index. Filling a select as though it were a text field does nothing — the native value setter belongs to HTMLInputElement and has no effect here — which is the silent failure this tool exists to prevent. Matches value first, then exact visible text, then a substring, then index. Returns {selected, value, text} for the chosen option, and on no match fails with the available options listed.
Inputs: selector (required), ref, text, index, +2 more.
session_snapshotAIdempotent
Capture a semantic map of a page for deciding what to act on. Returns {url, title, elements}, where each element is {ref, tag, text} — ref being an @eN handle that session_click, session_fill, session_type, session_select and session_press all accept in place of a CSS selector. Prefer this over session_read_page when the goal is to interact rather than to read: it lists only elements a user could actually operate. Skips zero-size and hidden elements, caps each label at 120 characters, and stops at 200 elements.
Inputs: tabId.
session_store_loginAIdempotent
Encrypt credentials for a domain and store them in the extension's vault, for session_login to use later. Requires the T3rnel Browser extension with Pro. The password is never returned by this or any other tool, and never appears in a listing or an error.
Inputs: domain (required), password (required), username (required), masterPassword.
session_typeA
Type text one character at a time, firing the key events a real keyboard would. Use this instead of session_fill when a field only reacts to keystrokes — search boxes with live suggestions, autocompletes, and inputs with per-character validation. Returns {typed} with the number of characters sent. Slower than session_fill, so reach for it only when session_fill leaves the page unchanged.
Inputs: text (required), selector (required), ref, tabId.
session_waitARead-onlyIdempotent
Block until a page reaches a known state, so the next tool acts on a settled page rather than a half-loaded one. Waits for the load event, for the URL to contain a string, or for a selector to appear. Returns as soon as the condition holds — {condition, waited} for load, {condition, url} for url, {condition, found} for selector — and fails at the timeout with a named error rather than hanging the client. Polls every 200ms; the default timeout is 10000ms.
Inputs: condition (required), tabId, value, timeoutMs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Thryv MCP server for ChatGPT, Claude and any AI agent: list appointments, book appointment, create invoice, add client and send message in your own Thryv account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Thryv yourself; Cotlet does not store your password and you need no Thryv API key. About the official Thryv API: Thryv Business Center has no public developer API (checked 11 Oct 2026). The only official way in from code is a Zapier connection with 4 triggers and 5 actions, authorized with a token that only the primary admin can see; the REST API Thryv documents is for Keap, its separate CRM. Setup and FAQ: https://cotlet.dev/integrations/thryv-api-mcp-server
TaxDome MCP server for ChatGPT, Claude and any AI agent: create job, request documents, send invoice, message client and list overdue tasks in your own TaxDome account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to TaxDome yourself; Cotlet does not store your password and you need no TaxDome API key. About the official TaxDome API: TaxDome has no public API that firms can use today (checked 14 Oct 2026). Its Zapier integration only creates, updates and finds contacts, and TaxDome MCP, which would let Claude or ChatGPT work in a firm account, is announced but not open yet and is offered to Professional and Business plan firms first. Setup and FAQ: https://cotlet.dev/integrations/taxdome-api-mcp-server
ServiceTrade MCP server for ChatGPT, Claude and any AI agent: list jobs, create appointment, release appointment to technicians, list deficiencies, create quote, submit quote and add comment to job in your own ServiceTrade account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ServiceTrade yourself; Cotlet does not store your password and you need no ServiceTrade API key. About the official ServiceTrade API: ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). The API covers jobs, appointments, deficiencies and quotes, so the missing piece is the agent layer: you build and host the wrapper yourself. Setup and FAQ: https://cotlet.dev/integrations/servicetrade-api-mcp-server
Substack MCP server for ChatGPT, Claude and any AI agent: create post, schedule post, publish Note, reply to Notes, send direct message, moderate comments, list subscribers and get post stats in your own Substack account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Substack yourself; Cotlet does not store your password and you need no Substack API key. About the official Substack API: Substack has only a limited API (checked 11 Oct 2026). Its Developer API looks up public creator profiles after approval, and there is no public API to write posts or Notes, manage subscribers or send email. Setup and FAQ: https://cotlet.dev/integrations/substack-api-mcp-server
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server + Chrome extension that drive the user's real, logged-in Chrome over a local WebSocket. 59 token-efficient web-dev tools: compact element refs instead of screenshots, server-side table filtering, visual regression, accessibility/SEO/security audits, network mocking. Also runs on ChromeOS/Crostini.691,161 npm7MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceLets AI coding tools drive the real, already-logged-in Chrome browser over local stdio—snapshotting and reading pages, clicking, typing, managing tabs, capturing screenshots, and inspecting network, console, storage, and cookies—without opening a remote-debugging port. It installs as a Chrome extension plus native-messaging bridge, so agents work in the user's authenticated sessions while passing bot detection.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive your real, already-logged-in Chrome — navigating, reading, clicking, filling forms, screenshotting, inspecting network traffic and cookies. Because it runs through a browser extension instead of a debugging port, it works on authenticated pages and passes bot detection without extra setup.1 npmISC