Skip to main content
Glama
Sign In
Playwright MCP

Playwright MCP

by hellokitty2520
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
      10,095,150 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
      10,095,150 npm
      Apache 2.0

    • Playwright MCP

      foxfoxfox789
      A
      license
      B
      quality
      C
      maintenance
      Enables AI tools to drive a hosted, headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots — without installing a browser locally or running npx on each machine. It runs as a single authenticated Render web service that any MCP client can connect to at a shared HTTPS endpoint.
      23
      10,095,150 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
      10,095,150 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
      10,095,150 npm
      Apache 2.0

    • Playwright MCP

      khbrfykhmsynh-dot
      A
      license
      B
      quality
      C
      maintenance
      Lets AI clients drive a real headless Chromium browser through a hosted HTTPS endpoint — navigating, clicking, typing, and reading pages via structured accessibility snapshots rather than screenshots. Requests are gated behind a bearer token, so no local browser install or npx is needed on each machine.
      23
      10,095,150 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.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clearly distinct browser actions and resources, with descriptions that help distinguish similar-sounding pairs. A few boundaries are softer, such as browser_drag vs browser_drop, browser_snapshot vs browser_take_screenshot, and browser_evaluate vs browser_run_code_unsafe, but these are mostly clarified by descriptions.

    Naming Consistency4/5

    All tools use a consistent browser_ prefix and snake_case, making the set predictable overall. Minor deviations exist: browser_tabs is a multiplexed noun-style tool, and a few read-only tools use noun phrases (browser_console_messages, browser_network_requests) rather than verb_noun action names.

    Tool Count4/5

    With 23 tools, the server is on the heavy side but still reasonably scoped for a full browser-automation surface. Each tool maps to a meaningful capability, though some could arguably be consolidated, such as fill_form/type/press_key or the network request pair.

    Completeness4/5

    The surface covers most browser-automation workflows: navigation, interaction, forms, uploads, drag/drop, snapshots, screenshots, console, network inspection, tabs, dialogs, and evaluation. Minor gaps remain, such as explicit forward navigation and cookie/storage management, but agents can generally work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources