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.
      246 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
      6,524,222 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.
      14 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

    A4.1/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool has a clear, singular purpose with minimal overlap. view_page and dom_snapshot are distinct (text/refs vs layout/geometry), and capture_image is explicitly limited to pixel-level content. The descriptions reinforce boundaries, so an agent should rarely misselect.

    Naming Consistency4/5

    The majority follow a verb_noun pattern (view_page, file_upload, fill_form, switch_tab), but there are single verbs (type, click, scroll, evaluate) and noun-only names (virtual_desk, console_logs). The consistent snake_case and predictable verb-first style keep it readable, though not perfectly uniform.

    Tool Count4/5

    At 25 tools, this is on the heavy end of the appropriate range. However, each tool addresses a distinct browser automation capability (navigation, interaction, waiting, dialogs, downloads, JS execution, network, etc.), so the count is justified by the breadth of the domain.

    Completeness5/5

    The surface is remarkably complete for browser automation: navigation, tab management, clicking, typing, forms, drag-and-drop, scrolling, waiting, dialogs, downloads, screenshots, DOM inspection, JS execution, network monitoring, console logs, file upload, session config, and batch evaluation. No critical gaps are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow