Skip to main content
Glama
johnjd059-cloud

Playwright MCP

by johnjd059-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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
      7,739,093 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

    • 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
      7,739,093 npm
      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.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but a few pairs overlap: browser_evaluate vs browser_run_code_unsafe both execute code, browser_take_screenshot vs browser_snapshot both capture page state, and browser_network_requests vs browser_network_request are related list/detail operations. These are distinguishable from descriptions, but an agent could still misselect in edge cases.

    Naming Consistency5/5

    All tool names use a consistent browser_ prefix followed by snake_case, with predictable verb_noun or action phrases. There is no mixing of conventions or casing styles, making the toolset easy to scan and remember.

    Tool Count4/5

    With 23 tools, the surface is large but reasonable for a full browser automation server covering navigation, interaction, forms, network, console, tabs, and screenshots. A few niche tools could be consolidated, but each broadly earns its place.

    Completeness4/5

    The set covers most browser automation needs: navigation, clicking, typing, form filling, keyboard, hover, select, drag/drop, file upload, dialogs, JavaScript evaluation, network inspection, console, tabs, waits, screenshots, and snapshots. Minor gaps exist, such as forward navigation and explicit reload, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources