Skip to main content
Glama

Related Servers

Alternatives to Public Browser

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.
      468 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A browser automation MCP server that enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or vision models.
      24
      5,425,474 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A token-optimized MCP server that groups Chrome Devtools tools into 8 semantic operations, reducing context window tokens by 69.5% while preserving full functionality.
      2 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -

    TDQS

    A3.8/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools map cleanly to distinct browser capabilities such as viewing, clicking, typing, scrolling, downloading, and evaluating JS. A few pairs like observe vs wait_for and view_page vs dom_snapshot have some conceptual overlap, but the descriptions do a good job of drawing boundaries.

    Naming Consistency3/5

    Names are consistently lowercase and snake_case, but the pattern is mixed: single verbs like click, type, and scroll sit alongside verb_noun names like view_page and fill_form, and noun-style names like virtual_desk, tab_status, and network_monitor. The set is readable but not stylistically uniform.

    Tool Count3/5

    25 tools is right at the heavy end of a reasonable browser-automation surface. Each tool addresses a legitimate need, but the count feels large, especially with separate tools for screenshots, DOM snapshots, console logs, network monitoring, and evaluate-style operations.

    Completeness4/5

    The toolset covers the full browser workflow: tab and navigation management, DOM reading, interaction, forms, waits, dialogs, uploads, downloads, network/console diagnostics, and JavaScript execution. Minor gaps like cookie/localStorage management, explicit frame switching, and hover could cause workarounds but do not block realistic tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow