Skip to main content
Glama
clanker25

Playwright MCP

by clanker25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

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.
      4,633,135 npm
      Apache 2.0

    • Playwright MCP

      DavidG-BLW
      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
      4,633,135 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.
      4,633,135 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.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and descriptions help differentiate similar ones like browser_snapshot vs browser_find and browser_evaluate vs browser_run_code_unsafe. The main minor overlaps are browser_close vs browser_tabs and browser_type vs browser_fill_form, which could cause occasional misselection.

    Naming Consistency4/5

    All tools share a consistent browser_ prefix and snake_case style, with most names following a verb-oriented pattern like browser_click, browser_hover, and browser_navigate. A few noun-style names like browser_network_requests, browser_snapshot, and browser_file_upload deviate slightly, but the overall pattern remains predictable.

    Tool Count4/5

    24 tools is on the heavier side for an MCP server, but the scope of browser automation justifies the breadth. Each tool addresses a real interaction need, though a few could potentially be consolidated without much loss.

    Completeness4/5

    The tool set covers the core browser automation lifecycle well: navigation, clicking, typing, form filling, snapshots, network inspection, dialogs, tabs, uploads, and JavaScript evaluation. Minor gaps like browser_forward and a more general wait-for-element tool are workable around with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources