Skip to main content
Glama
erlanov2023e

Playwright MCP

by erlanov2023e
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      uro31821-lab
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to drive a hosted headless Chromium browser over HTTP, letting them navigate pages, click, type, and read structured accessibility snapshots via the Model Context Protocol.
      23
      6,607,817 npm
      Apache 2.0

    • Playwright MCP

      1000carlospena-prog
      A
      license
      B
      quality
      C
      maintenance
      Enables LLMs to drive a hosted headless Chromium browser over HTTP, performing navigation, clicks, typing, and page reading through accessibility snapshots, protected by bearer-token authentication.
      23
      6,607,817 npm
      Apache 2.0

    • Playwright MCP

      junais-kandara
      A
      license
      B
      quality
      C
      maintenance
      Enables LLMs and MCP clients to control a hosted headless Chromium browser over HTTP, navigating, clicking, typing, and reading pages via structured accessibility snapshots, with bearer-token authentication.
      23
      6,607,817 npm
      Apache 2.0

    • Playwright MCP

      johnjd059-cloud
      A
      license
      B
      quality
      C
      maintenance
      Enables an LLM to control a hosted headless Chromium browser over HTTP, navigating pages, clicking, typing, and reading structured accessibility snapshots so any MCP client can perform browser automation without local installation.
      23
      6,607,817 npm
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool serves a distinct browser automation purpose: navigation, actions (click, hover, drag), input (type, press_key, fill_form), page inspection (snapshot, screenshot, network/console), and session management (tabs, resize, close). No two tools overlap in function; even similar tools like browser_evaluate and browser_run_code_unsafe are clearly separated by context (page vs server).

    Naming Consistency5/5

    All 23 tools follow the consistent pattern of 'browser_' prefix followed by a lowercase snake_case verb or verb phrase (e.g., browser_navigate, browser_network_requests). The naming is uniform, descriptive, and predictable, making it easy to infer tool behavior from the name alone.

    Tool Count3/5

    At 23 tools, the count falls in the 16–25 range, which feels heavy per calibration. However, the domain of browser automation is inherently broad, and each tool addresses a specific action or inspection need. Still, the number exceeds the typical well-scoped 3–15 range, meriting a borderline score.

    Completeness4/5

    The toolset covers core browser workflows comprehensively: navigation (navigate, back), user input (click, type, press_key, select_option, fill_form), page diagnostics (snapshot, screenshot, console, network), and browser management (tabs, resize, close). Minor gaps exist (e.g., no explicit 'reload' or 'go forward' tool), but these can be handled via browser_evaluate or browser_navigate, so the surface is largely complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources