Skip to main content
Glama
lebrodus

Playwright MCP Server

by lebrodus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Playwright MCP Server

No user-submitted related servers found.

    Related Servers

    • Playwright MCP Server

      apify
      A
      license
      Not graded
      quality
      F
      maintenance
      This server provides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots. It enables tasks like web navigation, form filling, and data extraction without the need for screenshots or vision-tuned models.
      4,622 npm
      4
      Apache 2.0

    • Puppeteer MCP Server

      twolven
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      18
      Apache 2.0

    • Playwright MCP Server

      BhanuTJ93
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in real browser environments.
      31
      12,163 npm
      MIT

    • Playwright MCP Server

      devskido
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.
      32
      12,163 npm
      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.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools cleanly separate into three categories: HTTP methods (GET, POST, PUT, PATCH, DELETE), browser interaction (click, fill, hover, navigate, screenshot, select), and JavaScript execution (evaluate). There is no overlap between these functional areas.

    Naming Consistency5/5

    All tools follow a perfect 'playwright_verb' naming pattern with consistent snake_case throughout. The verb choices are precise and descriptive (click, fill, hover, navigate, evaluate, screenshot, select, get, post, put, patch, delete), creating a highly predictable and readable naming convention.

    Tool Count5/5

    12 tools is well-scoped for a Playwright automation server. The count provides comprehensive coverage of core browser automation and HTTP testing capabilities without being overwhelming. Each tool clearly earns its place in the toolkit.

    Completeness4/5

    The tool surface is nearly complete for browser automation and HTTP testing. It covers navigation, interaction, JavaScript execution, screenshots, and full HTTP method support. Minor gaps might include waiting/retry mechanisms or file upload/download operations, but core workflows are well covered.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources