Skip to main content
Glama
1000carlospena-prog

Playwright MCP

by 1000carlospena-prog
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

    • 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
      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
    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

    Disambiguation5/5

    Each tool has a clear, unique action (navigate, click, type, wait, screenshot, network, etc.) with no overlapping purposes. Even similar tools like type vs press_key vs fill_form are distinct in their behavior.

    Naming Consistency5/5

    All tools follow the consistent 'browser_' prefix with snake_case naming. The pattern is uniform across verbs and nouns, making it easy to predict tool names.

    Tool Count4/5

    23 tools is slightly above the typical 3-15 range, but justified for a comprehensive browser automation server. The number is not excessive and each tool contributes meaningful functionality.

    Completeness4/5

    The toolset covers core browser interactions (navigation, clicks, typing, waiting, screenshots, network, tabs, file upload) and also advanced features (JS evaluation, dialogs, drag-and-drop). Missing some niche actions like scrolling or cookie management, but these are often accessible via evaluate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources