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.
      66
      733 npm
      5
      MIT

    • Pagewright (browser-mcp)

      zamansheikh
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.
      14 npm
      1
      MIT

    • browser-mcp-lite

      lu4nn3ry
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive a real Chrome instance over the Chrome DevTools Protocol — opening and navigating tabs, reading compact YAML page outlines with refs, clicking, typing, scrolling, screenshotting, and evaluating scripts — with no browser extension or installed dependencies. It also audits pages for horizontal overflow and WCAG AA contrast, available both as an MCP tool and as a CI-friendly CLI.
      12 npm
      MIT

    • Scout

      klarlabs-studio
      A
      license
      Not graded
      quality
      A
      maintenance
      single-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.
      13
      MIT

    • kilogent-browser

      codebridger
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.0

    • Chromeflow

      NeoDrew
      A
      license
      Not graded
      quality
      A
      maintenance
      Chrome extension + MCP server. Lets coding agents (Claude Code, Codex CLI) drive your real Chrome — sessions intact, 2FA stays with the user. 26 browser tools: form fill on React/CodeMirror/Monaco, privileged fetch that bypasses page CSP, authenticated downloads, in-extension docx parsing. Battle-tested by 400+ hours of real agentic browser work before public v0.9 release.
      29 npm
      2
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.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