Skip to main content
Glama
1000carlospena-prog

Playwright MCP

by 1000carlospena-prog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      erlanov2023e
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to remotely drive a hosted headless browser over HTTP, supporting navigation, clicking, typing, and structured page reading through the Model Context Protocol. It also provides bearer-token authentication for secure remote MCP access.
      23
      5,046,799 npm
      Apache 2.0

    • Playwright MCP Server

      tomscoppock
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.
      Apache 2.0

    • WebControl

      matanSht
      F
      license
      Not graded
      quality
      C
      maintenance
      Headless browser automation for LLM agents via REST API or MCP tools. Enables navigating pages, reading structured content, clicking elements, filling forms, and executing JavaScript.
      -

    • 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,591 npm
      4
      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 23 tools

    Disambiguation4/5

    Most tools target distinct browser actions, and descriptions clarify similarities like snapshot vs screenshot or network_requests vs network_request. A few pairs (e.g., browser_type vs browser_fill_form, browser_drag vs browser_drop) could be confused in edge cases, but the boundaries are generally clear.

    Naming Consistency4/5

    All tools share a consistent browser_ prefix, and most follow a verb_noun pattern like browser_navigate, browser_click, and browser_select_option. A few noun-style names (browser_console_messages, browser_network_requests, browser_snapshot, browser_tabs) deviate from this pattern, creating minor inconsistency.

    Tool Count4/5

    23 tools is on the heavier side but reasonable for a browser automation server covering navigation, interaction, input, network inspection, dialogs, and screenshots. Each tool serves a distinct purpose and the count is not bloated relative to the domain's complexity.

    Completeness4/5

    The tool surface covers the core browser automation lifecycle: navigation, interaction, forms, tabs, dialogs, screenshots, network inspection, and JavaScript evaluation. Obvious minor gaps include no navigate_forward, reload, cookie handling, or localStorage access, but these can be worked around with browser_evaluate or browser_navigate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources