Skip to main content
Glama
t3ratech

T3rnel Browser — Session Bridge

Official
by t3ratech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to T3rnel Browser — Session Bridge

No user-submitted related servers found.

    Related Servers

    • Chrome Bridge

      frsorrentino
      A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      69
      1,840 npm
      6
      MIT

    • byob

      timothynowak98572
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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 npm
      ISC

    • byob

      Jasonz68342
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to drive the user's real, already-logged-in Chrome through an MCP stdio interface, exposing 25 tools for navigating, clicking, typing, reading pages, taking screenshots, capturing network traffic, and accessing cookies and storage. The bundled Chrome extension talks to a local bridge instead of an open remote-debugging port, so logged-in sessions and bot-detection-proof human browsing work without extra setup.
      1 npm
      ISC

    • PolterTab

      abhinav162
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server paired with a Chrome extension that lets any MCP-compatible AI agent drive the browser you're already signed into — navigating, clicking, filling forms, scraping and extracting structured records using your real profile, cookies and logged-in sessions. It exposes 28 browser_* tools over stdio and relays them to the extension on localhost, with capabilities like paginated record extraction, ref-tagged snapshots, screenshots, and opt-in file uploads.
      2,033 npm
      1
      ISC

    • byob

      melissa89018
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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 npm
      ISC

    • byob

      yoko593
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets 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 npm
      ISC
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A4.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources