Skip to main content
Glama

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a real Chromium browser over MCP using genuine mouse, keyboard, and wheel input, with accessibility snapshots, diffs, network logs, forked sessions, and replayable traces for bug bounty hunting.
      8
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A browser automation MCP server that enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or vision models.
      24
      3,465,430 npm
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive a Chromium browser over MCP, reading pages as a numbered list of controls and performing actions like clicking, filling forms, and asserting page state without screenshots or API keys.
      10
      76 PyPI
      20
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables an LLM to control a hosted headless Chromium browser over HTTP, navigating pages, clicking, typing, and reading structured accessibility snapshots so any MCP client can perform browser automation without local installation.
      23
      3,465,430 npm
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct browser-automation purposes, but a few boundaries blur: browser_close vs. browser_tabs can both close tabs, and browser_evaluate vs. browser_run_code_unsafe both execute code in different contexts. The descriptions usually clarify these differences, though an agent may still hesitate in edge cases.

    Naming Consistency5/5

    All tool names use a consistent browser_ prefix followed by snake_case verbs or noun phrases. The pattern is predictable throughout the set.

    Tool Count3/5

    25 tools is at the heavy end for a browser automation server; while most operations are genuinely useful, the surface feels granular and borderline overloaded. A more compact set could combine several low-level controls without losing capability.

    Completeness4/5

    The surface covers navigation, interaction, forms, screenshots, snapshots, tabs, dialogs, uploads, network/console inspection, and code execution. Minor gaps exist, such as explicit forward navigation/reload and cookie/storage management, but agents can often work around them with evaluate or run_code_unsafe.

    Maintenance

    ActivityActive
    ResponsivenessNo issues