Skip to main content
Glama

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation through Playwright, enabling LLMs to interact with web pages using structured accessibility snapshots instead of screenshots.
      5,046,799 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots without needing vision models.
      5,046,799 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots without needing screenshots or vision models.
      2
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without screenshots.
      24
      5,046,799 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation capabilities for LLMs using Playwright, leveraging structured accessibility snapshots to interact with web pages without needing vision models. It enables tasks like web navigation, data extraction, and automated testing through a lightweight and deterministic toolset.
      6 npm
      Apache 2.0

    TDQS

    B3.1/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct browser action or resource: navigation, interaction, snapshotting, network inspection, dialog handling, etc. Even the paired tools like browser_network_requests/browser_network_request and browser_find/browser_snapshot are clearly separated by list/detail and search/full-snapshot purposes. No two tools overlap in functionality.

    Naming Consistency4/5

    All tools share the 'browser_' prefix, which provides a strong visual grouping. However, the second part mixes verb forms (browser_navigate, browser_click) with noun forms (browser_console_messages, browser_tabs), and some tools use verb_noun while others use verb alone. This is mostly predictable but not perfectly uniform.

    Tool Count4/5

    With 24 tools, the set is on the heavier side, but every tool addresses a common browser automation scenario—navigation, element interaction, input, screenshots, network, tabs, and dialogs. The count is justified for a comprehensive Playwright wrapper, and none of the tools feel redundant.

    Completeness4/5

    The tool surface covers the core browser lifecycle: navigation, interaction, input, snapshotting, console/network inspection, tab management, and dialog handling. Obvious gaps include dedicated scrolling, element attribute inspection, and download management, but these can be worked around via browser_evaluate. Overall, the set is complete enough for most automation workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues