Skip to main content
Glama

Related Servers

Alternatives to chrome-session-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to access authenticated websites by reusing your existing browser profile and cookies, so you never share passwords and sessions persist between runs.
      5
      5
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.
      40
      64
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to drive the real Chrome browser you already have open — navigating, clicking, typing, reading pages, taking screenshots, and inspecting cookies, network traffic, and storage from within your existing logged-in sessions. All communication stays local to your machine.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to drive the user's real, already-logged-in Chrome browser locally, so they can read and navigate pages, click, type, fill forms, take screenshots, and inspect cookies, tabs, console, and network traffic without headless browsers or remote-debugging ports.
      1 npm
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control the user's Chrome or Firefox browser, leveraging existing sessions for tasks requiring authentication and user handoff.
      18
      47 npm
      21
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets 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 npm
      ISC

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct concern: config inspection (list_connectors), passive session checking (auth_status), active login (login), and opening a URL for the user (open_in_browser). The only mild overlap is auth_status vs login, but descriptions clearly separate passive checking from performing a login.

    Naming Consistency3/5

    Names use three different patterns: verb_noun (list_connectors, open_in_browser), noun_phrase (auth_status), and a bare verb (login). Still readable and each name hints at its purpose, but the convention is mixed.

    Tool Count5/5

    Four tools are tightly scoped to the server's apparent purpose of managing authenticated Chrome sessions. Each tool has a clear, non-redundant role with no filler.

    Completeness4/5

    The session lifecycle (discover connectors, check status, log in, use the session to open pages) is covered. Minor gaps exist, such as no logout/clear-session or a tool to programmatically read page content from a connector, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues