Skip to main content
Glama
williamvd4

Playwright Server

by williamvd4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Playwright Server

No user-submitted related servers found.

    Related Servers

    • Playwright Server MCP

      ziux
      A
      license
      B
      quality
      D
      maintenance
      A browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.
      6
      Apache 2.0

    • Playwright SSE MCP Server

      torohash
      F
      license
      Not graded
      quality
      D
      maintenance
      A service that provides Playwright browser automation functionality through Model Context Protocol (MCP), allowing clients to use Playwright features via SSE connections.
      7
      -

    • Fetch MCP

      jae-jae
      A
      license
      B
      quality
      F
      maintenance
      An MCP server that retrieves web page content using Playwright headless browser, capable of extracting main content and converting to Markdown format.
      3
      3,627 npm
      1,087
      MIT

    • Browser-MCP Server

      Euraxluo
      A
      license
      C
      quality
      D
      maintenance
      A session-based MCP server that provides advanced browser automation capabilities, allowing users to control browsers, navigate websites, interact with elements, capture screenshots, generate PDFs, and manage cookies through natural language.
      35
      1
      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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. For example, playwright_click targets elements by CSS selector while playwright_click_text uses text content, and tools like playwright_get_html_content versus playwright_get_text_content provide different types of content retrieval. The descriptions clearly differentiate the specific actions each tool performs.

    Naming Consistency5/5

    All tools follow a consistent 'playwright_verb' pattern with snake_case throughout. The naming is perfectly predictable, starting with 'playwright_' followed by an action verb that accurately describes the tool's function, such as 'click', 'evaluate', 'fill', or 'navigate'.

    Tool Count5/5

    With 8 tools, this server is well-scoped for browser automation tasks. Each tool earns its place by covering essential operations like navigation, interaction (clicking, filling), content retrieval (HTML, text), and utilities (screenshot, JavaScript execution). This count is ideal for the domain without being overwhelming or insufficient.

    Completeness4/5

    The toolset covers core browser automation workflows effectively, including navigation, element interaction, content extraction, and screenshots. Minor gaps exist, such as no explicit tool for waiting or handling alerts, but agents can work around these using existing tools like playwright_evaluate for JavaScript-based solutions. The surface is largely complete for the stated purpose.

    Resources