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
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables any MCP client to drive a hosted headless Chromium browser over HTTPS — navigating, clicking, typing, and reading pages via structured accessibility snapshots — with no local browser install or npx required. It runs as a single Render web service behind a bearer-token gate, since upstream ships no authentication of its own.
      23
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI clients to drive a hosted headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots rather than screenshots. Runs as a single authenticated web service, so any MCP client can connect to a shared HTTPS URL without installing a local browser.
      23
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Provides a hosted, bearer-token-protected HTTP endpoint where any MCP client can drive a headless Chromium instance — opening pages, navigating, clicking, typing, and reading content through accessibility snapshots — without installing a browser or Node locally. It runs the official server image as a single Render web service, so browser automation is reachable over a shared HTTPS URL.
      23
      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
      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
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target a clearly distinct action (click, hover, type, select_option, navigate, resize), and the network_requests/network_request pair is explicitly differentiated by description. Minor overlap exists between browser_type and browser_fill_form (single vs multiple fields), browser_drag and browser_drop (internal vs external source), and browser_evaluate vs browser_run_code_unsafe (both execute code), but these are adequately disambiguated in practice.

    Naming Consistency5/5

    Every tool follows a uniform browser_ snake_case verb/noun pattern (browser_navigate, browser_take_screenshot, browser_select_option). No deviations to camelCase or alternative prefixes, making the naming fully predictable.

    Tool Count4/5

    23 tools is on the heavier side of the ideal band, but a full browser-automation surface legitimately needs navigation, interaction, form, media, network, tab, and dialog operations. Each tool maps to a real capability, so the count is justified rather than bloated.

    Completeness4/5

    Coverage spans navigation/history, interaction (click, hover, drag, drop, type, select, press_key), forms, file upload, screenshots/snapshots, console, network inspection, tabs, dialogs, and waiting. Gaps like cookie/localStorage/session-storage management and viewport sizing via dedicated tools are minor and workable around.