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 tools to drive a hosted, headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots — without installing a browser locally or running npx on each machine. It runs as a single authenticated Render web service that any MCP client can connect to at a shared HTTPS endpoint.
      23
      8,508,652 npm
      Apache 2.0
    • 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
      8,508,652 npm
      Apache 2.0
    • 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
      8,508,652 npm
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables LLMs and MCP clients to control a hosted headless Chromium browser over HTTP, navigating, clicking, typing, and reading pages via structured accessibility snapshots, with bearer-token authentication.
      23
      8,508,652 npm
      Apache 2.0
    • 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
      8,508,652 npm
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target distinct actions (click, type, hover, drag, select_option). A few pairs require careful reading to distinguish: browser_evaluate vs browser_run_code_unsafe, browser_type vs browser_fill_form, and browser_drop vs browser_drag, though the descriptions do clarify the differences.

    Naming Consistency5/5

    Every tool uses the browser_ prefix with snake_case verb_noun naming (browser_navigate, browser_take_screenshot, browser_press_key). The convention is applied uniformly across all 23 tools with no deviations.

    Tool Count4/5

    23 tools is on the heavier side but justified for full browser automation, each mapping to a distinct capability. Not bloated, though slightly above the comfortable range.

    Completeness4/5

    Strong lifecycle coverage: navigation, interaction, forms, dialogs, network/console inspection, screenshots, snapshots, and tabs. Minor gaps like cookie/storage/localStorage management and explicit hover-state assertions, but core workflows are fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues