Skip to main content
Glama
rdatri-ux

Playwright MCP

by rdatri-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      erlanov2023e
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to remotely drive a hosted headless browser over HTTP, supporting navigation, clicking, typing, and structured page reading through the Model Context Protocol. It also provides bearer-token authentication for secure remote MCP access.
      23
      5,046,799 npm
      Apache 2.0

    • arthur

      sh7vansh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control a headless Chromium browser through a persistent Python REPL, providing navigation, interaction, snapshotting, and media control via the Model Context Protocol.
      MIT

    • openmcp

      openmcp-pro
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate web tasks such as browsing, clicking, typing, and taking screenshots via the Model Context Protocol.
      1
      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

    Disambiguation4/5

    Most tools target distinct browser actions (click, type, hover, drag, drop, etc.), and descriptions clarify edge cases like snapshot vs screenshot. However, browser_drag vs browser_drop and browser_type vs browser_press_key could still cause occasional misselection without careful reading.

    Naming Consistency3/5

    All tools share a consistent browser_ prefix and snake_case style, but the action part is mixed: verbs (browser_close, browser_evaluate) coexist with nouns (browser_snapshot, browser_network_requests, browser_tabs). This is readable but not a uniform verb_noun pattern.

    Tool Count4/5

    23 tools is on the heavier side but justified for a full-featured browser automation server covering navigation, input, inspection, network, tabs, and dialogs. A few tools like browser_network_requests/request could arguably be merged, but the count is not excessive.

    Completeness4/5

    The toolset covers most core browser automation workflows, including navigation, clicking, typing, forms, screenshots, and network inspection. Minor gaps like dedicated checkbox/radio interaction or page reload are missing, but agents can work around them via browser_click or browser_evaluate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources