Skip to main content
Glama
maywzh

Playwright MCP

by maywzh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      korwabs
      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.
      6
      Apache 2.0

    • Playwright MCP Server

      AkhatorKing1
      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
      24,322 npm
      Apache 2.0
    • Fetch MCP Server by modelcontextprotocol

      Fetch MCP Serverofficial

      modelcontextprotocol
      A
      license
      A
      quality
      A
      maintenance
      This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
      2
      1
      117,055 PyPI
      90,629
      MIT

    • WebMCP

      jasonjmcghee
      A
      license
      Not graded
      quality
      C
      maintenance
      A framework that enables websites to share tools, resources, and prompts with client-side LLMs without requiring API keys, allowing users to interact with web services using their preferred models.
      376 npm
      851
      MIT
    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

    A3.6/5.0

    Scored across 24 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific browser interaction (click, navigate, screenshot, etc.) or management task (install, close, resize), and descriptions clarify any potential overlaps (e.g., browser_snapshot vs. browser_take_screenshot).

    Naming Consistency5/5

    Tool names follow a highly consistent 'browser_verb_noun' pattern throughout (e.g., browser_click, browser_navigate, browser_tab_list). All tools use snake_case with 'browser_' prefix, making them predictable and readable.

    Tool Count4/5

    With 24 tools, the count is slightly high but reasonable for a comprehensive web automation server. It covers a wide range of interactions (navigation, input, tabs, debugging) without obvious bloat, though it borders on the upper limit of typical scoping.

    Completeness5/5

    The toolset provides complete coverage for web automation and testing. It includes core navigation, user interactions (click, type, drag), tab management, debugging (console, network), media capture (screenshot, snapshot), and utilities (wait, install), leaving no obvious gaps for the domain.

    Resources