Skip to main content
Glama

Related Servers

Alternatives to autologin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding tools to drive the user's real, already-logged-in Chrome browser — reading pages, clicking, typing, navigating tabs, screenshots, and cookie, network, and storage access — without opening a remote-debugging port.
      1 npm
      ISC
    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.
      335 npm
      610
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents a single shared, logged-in Chrome they can drive over MCP or plain HTTP: open and read tabs, click, type, upload files, run short Playwright scripts, hand off whole web tasks to a cheaper model, and keep per-site memory. Agents work in background windows they own without stealing the user's mouse or closing their tabs.
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct step of the login workflow: listing profiles, performing login, checking outcome, and editing config. The only potential overlap is between `login` and `login_status`, but the description explicitly scopes `login_status` to the fallback case where the `run_in_page` script fails.

    Naming Consistency4/5

    All names use snake_case and are short and predictable, with `list_profiles`, `login_status`, and `open_config` following an action-oriented pattern. `login` alone is a bare verb without a noun complement, a minor deviation from the rest of the set.

    Tool Count5/5

    Four tools is well-matched to a narrow, single-purpose server (automated credential-based login). Every tool maps to a distinct step of the flow, with no redundant or filler operations.

    Completeness3/5

    Core login and profile-listing are covered, but profile lifecycle management is deferred entirely to `open_config` opening a text editor, so an agent cannot add, edit, or remove profiles programmatically. There is also no logout/session-invalidation or profile validation tool, leaving some dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues