Skip to main content
Glama
Sign In
Playwright MCP

Playwright MCP

by khbrfykhmsynh-dot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

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

    • 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

      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
    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 target clearly distinct actions (click, hover, navigate, screenshot), and descriptions help distinguish close pairs like snapshot vs. screenshot and network_requests vs. network_request. However, several clusters overlap—type/fill_form/press_key, drag/drop/file_upload, and evaluate/run_code_unsafe—which could occasionally cause misselection.

    Naming Consistency5/5

    All 23 tools use a consistent browser_ prefix with snake_case, making the set predictable and easy to scan. The pattern mixes verb-based and noun-based names (browser_click vs. browser_snapshot), but the convention itself is stable throughout.

    Tool Count4/5

    23 tools is slightly heavy for the typical 3-15 range, but each maps to a distinct Playwright action needed for full browser automation. There is no obvious redundancy, though a few tools (drop vs. drag, evaluate vs. run_code_unsafe) could potentially be consolidated.

    Completeness4/5

    The surface covers navigation, interaction, forms, dialogs, network inspection, screenshots/snapshots, tabs, and waits—a comprehensive lifecycle for browser automation. Minor gaps include no forward-navigation counterpart to browser_navigate_back and no explicit scroll tool, though browser_evaluate can work around both.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources