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 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
      8,987,267 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,987,267 npm
      Apache 2.0
    • 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
      8,987,267 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.
      Apache 2.0
    • A
      license
      Not graded
      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.
      8,987,267 npm
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target clearly distinct browser actions, but several pairs have related purposes: browser_network_requests vs browser_network_request (list vs detail), browser_type vs browser_fill_form (single vs multiple inputs), and browser_take_screenshot vs browser_snapshot. Descriptions help, but an agent could still misselect in edge cases.

    Naming Consistency4/5

    All tool names use snake_case with a consistent 'browser_' prefix, which is predictable. However, some names are verb phrases (browser_navigate, browser_click) while others are noun phrases (browser_tabs, browser_snapshot, browser_console_messages), so the verb_noun pattern is not fully uniform.

    Tool Count3/5

    23 tools is on the heavy side for a single server, placing it in the borderline range (16-25). The domain is broad, so the count is defensible, but it exceeds the ideal 3-15 scoped range.

    Completeness4/5

    The surface covers navigation, interaction, inspection, dialogs, tabs, and file upload/drag-drop, which is nearly complete for browser automation. Minor gaps exist, such as forward navigation (only browser_navigate_back is present) and explicit cookie/storage management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues