Skip to main content
Glama
moctezumagit

Playwright MCP

by moctezumagit
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
      D
      maintenance
      Enables LLMs to interact with web pages through structured accessibility snapshots using Playwright, providing fast and lightweight browser automation without needing vision models.
      8,508,652 npm
      Apache 2.0

    • Playwright MCP

      DavidG-BLW
      A
      license
      B
      quality
      C
      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
      8,508,652 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.
      8,508,652 npm
      Apache 2.0
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.2/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target clearly distinct browser actions or resources, and descriptions help separate close cases like snapshot vs screenshot vs find. The main ambiguity is between browser_evaluate and browser_run_code_unsafe, which both execute code in different contexts, and browser_type vs browser_fill_form overlap somewhat.

    Naming Consistency4/5

    All tools use a consistent browser_ prefix and snake_case, making the surface easy to scan. There are minor deviations in action-vs-resource naming, such as browser_tabs, browser_console_messages, and browser_network_requests, plus the verb-noun inversion in browser_file_upload.

    Tool Count3/5

    At 25 tools, the surface is at the heavy end for a browser automation server. Most tools are justified, but some could be consolidated, such as the network request list/detail pair and the code execution tools.

    Completeness4/5

    The set covers a broad browser automation lifecycle: navigation, interaction, forms, dialogs, tabs, waiting, screenshots, snapshots, console, and network inspection. Minor gaps remain around cookies/storage, downloads, and iframe-specific operations, but core workflows are well supported.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources