Skip to main content
Glama
J0from

Playwright MCP

by J0from
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      priyshi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to interact with web pages through structured accessibility snapshots using Playwright, providing fast and lightweight browser automation without needing vision models.
      5,425,474 npm
      Apache 2.0

    • Playwright MCP

      mattreya
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform browser automation and web page interactions using Playwright's accessibility tree instead of screenshots. Provides fast, deterministic web automation through structured data without requiring vision models.
      5,425,474 npm
      Apache 2.0

    • Playwright MCP

      sasakiblog26-lgtm
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation capabilities for LLMs using Playwright's accessibility tree, enabling web page interaction through structured data without vision models.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct browser action or resource. Overlapping operations like browser_type vs browser_fill_form are clearly differentiated by scope (single element vs multiple fields), and browser_snapshot vs browser_take_screenshot explicitly separate accessibility tree captures from visual screenshots. No two tools present meaningful ambiguity.

    Naming Consistency5/5

    All tools share the 'browser_' prefix followed by a clear verb or verb phrase, using consistent snake_case throughout (e.g., browser_navigate, browser_fill_form, browser_network_request). Even multi-word names like browser_run_code_unsafe remain readable and predictable.

    Tool Count4/5

    24 tools is above the typical 15-tool sweet spot, but the browser automation domain requires diverse actions including navigation, interaction, network inspection, dialogs, and tab management. Each tool earns its place, and the count feels slightly heavy but justified rather than bloated.

    Completeness4/5

    The tool set covers core browser workflows: navigate, interact (click/type/hover/select/drag/drop), wait, snapshot/screenshot, evaluate, handle dialogs, file upload, and network/console inspection. A few minor gaps exist, such as no explicit 'browser_forward' or 'browser_reload', but these can be worked around via navigation or evaluation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources