Skip to main content
Glama

Related Servers

Alternatives to Playwright MCP

No user-submitted related servers found.

    Related Servers

    • 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,188,231 npm
      Apache 2.0
    • 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,188,231 npm
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to drive a hosted headless Chromium browser over HTTP, letting them navigate pages, click, type, and read structured accessibility snapshots via the Model Context Protocol.
      23
      10,188,231 npm
      Apache 2.0
    • 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
      10,188,231 npm
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation3/5

    While most tools have distinct purposes, browser_type, browser_press_key, and browser_fill_form overlap in typing interactions, and browser_drop vs browser_drag could cause confusion. browser_run_code_unsafe is clearly distinct but its purpose is not aligned with typical browser automation.

    Naming Consistency5/5

    All tools follow a consistent 'browser_' prefix with a clear verb_noun pattern (e.g., browser_navigate, browser_click, browser_take_screenshot). The naming is uniform and easy to predict.

    Tool Count3/5

    23 tools is slightly above the typical well-scoped range (3-15), but given the breadth of browser automation (navigation, interaction, input, network, tabs), it is justified. The count is on the heavier side but not excessive.

    Completeness4/5

    The tool surface covers core browser automation needs: navigation, interactions, input, screenshots/snapshots, dialogs, uploads, downloads, and network inspection. Minor gaps exist such as cookie management and form reset, but agents can work around them using browser_run_code_unsafe.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues