Skip to main content
Glama
Elvis280

Playwright MCP

by Elvis280
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • 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
      5,425,474 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

    • Fast Browser MCP

      kqlio67
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      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.2/5.0

    Scored across 23 tools

    Disambiguation3/5

    While most tools have distinct purposes, browser_type, browser_press_key, and browser_fill_form overlap in typing interactions, and browser_drop vs browser_drag could cause confusion. browser_run_code_unsafe is clearly distinct but its purpose is not aligned with typical browser automation.

    Naming Consistency5/5

    All tools follow a consistent 'browser_' prefix with a clear verb_noun pattern (e.g., browser_navigate, browser_click, browser_take_screenshot). The naming is uniform and easy to predict.

    Tool Count3/5

    23 tools is slightly above the typical well-scoped range (3-15), but given the breadth of browser automation (navigation, interaction, input, network, tabs), it is justified. The count is on the heavier side but not excessive.

    Completeness4/5

    The tool surface covers core browser automation needs: navigation, interactions, input, screenshots/snapshots, dialogs, uploads, downloads, and network inspection. Minor gaps exist such as cookie management and form reset, but agents can work around them using browser_run_code_unsafe.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources