Skip to main content
Glama

Related Servers

Alternatives to @playwright/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually tuned models.
      7
      17,093 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually-tuned models.
      7
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities by allowing LLMs to interact with web pages through structured accessibility snapshots. It enables fast, lightweight interaction with web content without the need for vision-tuned models or visual processing.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for lightweight browser automation using Lightpanda with Chrome fallback, providing LLM-optimized accessibility tree snapshots for precise element targeting.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides browser automation capabilities, enabling LLMs to control a web browser for navigation, interaction, and data extraction.
      32
      130 npm
      14
      MIT

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Overlapping operations like browser_snapshot and browser_take_screenshot are explicitly differentiated in descriptions. No two tools cause ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'browser_verb_noun' pattern (e.g., browser_click, browser_navigate_back, browser_file_upload). The naming is predictable and uniform.

    Tool Count4/5

    23 tools cover a wide range of browser automation operations without being excessive. The count is appropriate for the domain, though slightly on the higher side.

    Completeness4/5

    The tool set covers most essential browser interactions: navigation, clicking, typing, forms, screenshots, dialogs, tabs, network requests, and more. Minor gaps exist (e.g., cookie management, scrolling), but the surface is comprehensive.