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
      5,046,799 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
      Provides AI clients with deterministic Playwright-driven browser control, enabling navigation, interaction, screenshots, and inspection of rendered HTML, computed styles, console diagnostics, and font audits without an embedded LLM or API key.
      MIT
    • 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
      5,046,799 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables browser automation through a persistent Chrome instance exposed via HTTP, including navigation, screenshots, clicks, typing, multi-tab and multi-profile management, proxy switching, login state export, and AI-driven task execution.
      -

    TDQS

    B3.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes, but a few pairs overlap in function: browser_type vs browser_fill_form, browser_file_upload vs browser_drop, and browser_evaluate vs browser_run_unsafe_code could cause confusion about which to use for similar actions.

    Naming Consistency4/5

    All tools share the browser_ prefix and most follow a verb_noun pattern, but some are noun-based (browser_console_messages, browser_network_requests, browser_tabs) and a few names like browser_file_upload and browser_snapshot are less verb-oriented, creating minor inconsistency.

    Tool Count4/5

    23 tools is on the heavier side but reasonable for a browser automation server covering navigation, interaction, network inspection, console, dialogs, screenshots, and tab management. It is not needlessly bloated.

    Completeness4/5

    The set covers the core browser automation workflow well: navigation, clicking, typing, selecting, waiting, screenshots, network, console, dialogs, uploads, and tabs. Minor gaps like browser_forward, browser_reload, or an explicit new-page tool prevent a perfect score.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues