Skip to main content
Glama
foxfoxfox789

Playwright MCP

by foxfoxfox789
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      arsenygrozny-blip
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants and MCP clients to drive a hosted headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages via structured accessibility snapshots rather than screenshots. Runs as a Render web service behind a bearer-token gate, so no local browser install or npx setup is required on each machine.
      23
      5,364,110 npm
      Apache 2.0

    • Playwright MCP

      khbrfykhmsynh-dot
      A
      license
      B
      quality
      C
      maintenance
      Enables AI clients to drive a hosted headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots rather than screenshots. Runs as a single authenticated web service, so any MCP client can connect to a shared HTTPS URL without installing a local browser.
      23
      5,364,110 npm
      Apache 2.0

    • Playwright MCP

      arsenygrozny-blip
      A
      license
      B
      quality
      C
      maintenance
      Provides a hosted, bearer-token-protected HTTP endpoint where any MCP client can drive a headless Chromium instance — opening pages, navigating, clicking, typing, and reading content through accessibility snapshots — without installing a browser or Node locally. It runs the official server image as a single Render web service, so browser automation is reachable over a shared HTTPS URL.
      23
      5,364,110 npm
      Apache 2.0

    • Playwright MCP

      hellokitty2520
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to drive a hosted headless Chromium browser over HTTPS — navigating, clicking, typing, and reading pages via structured accessibility snapshots — with no local browser install or npx required. It runs as a single Render web service behind a bearer-token gate, since upstream ships no authentication of its own.
      5,364,110 npm
      Apache 2.0

    • Playwright MCP

      khbrfykhmsynh-dot
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to drive a real headless Chromium browser over a hosted HTTP endpoint, navigating, clicking, typing, and reading pages through structured accessibility snapshots rather than screenshots. Runs as a remote service authenticated with a bearer token, so no local browser install or per-machine setup is needed.
      23
      5,364,110 npm
      Apache 2.0
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (click, hover, drag, navigate, type). A few pairs risk confusion: browser_network_requests vs browser_network_request (singular/plural), browser_drag vs browser_drop, and browser_type vs browser_fill_form, though descriptions give some guidance.

    Naming Consistency5/5

    Every tool uses the browser_ prefix with snake_case and an action-oriented name, forming a highly predictable pattern. The singular/plural network tools are the only minor wrinkle but still follow the convention.

    Tool Count4/5

    23 tools is on the heavier side but each maps to a genuine browser-automation capability (navigation, input, forms, dialogs, network, console, snapshots, tabs, waiting). It's reasonable for the breadth of the domain rather than redundant.

    Completeness4/5

    Coverage spans navigation, interaction, form filling, file upload/drag, dialogs, network and console inspection, screenshots, and tab management—solid for browser automation. Minor gaps like forward navigation and explicit cookie/storage or viewport-state management are workarounds via evaluate/run_code.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources