Skip to main content
Glama
DailyNoBug

Playwright Browser MCP Server

by DailyNoBug

Related Servers

Alternatives to Playwright Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A high-performance browser automation MCP server that provides AI agents with a fast, persistent Chromium instance via Playwright. It features reference-based element interaction, snapshot diffing, and manual handoff capabilities to handle complex tasks like CAPTCHAs.
      61
      13 npm
      32
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Browser MCP server that connects to your existing browser, preserving sessions, passwords, and extensions, enabling AI agents to interact with web pages without bot detection.
      31
      7 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      19 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.
      51
      203 PyPI
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI clients a Steel-managed Chromium browser to read pages that block plain fetch, take screenshots, and interact with sites via clicking, typing, and form filling, with explicit browser sessions and access to the accessibility tree or markdown.
      MIT

    TDQS

    B3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Each tool targets a distinct action or resource, from session lifecycle to page interaction to extraction. While there are many extraction tools, their outputs (text, table, form, snapshot, interactive elements) are clearly differentiated. Some related tools like pause_for_human and get_human_wait_state have clear boundaries.

    Naming Consistency4/5

    All tools follow a snake_case verb_noun pattern, with consistent prefixes for domain areas (session, auth, extraction). Minor inconsistencies exist between 'get', 'extract', and 'snapshot' verbs, but they are still predictable.

    Tool Count2/5

    With 28 tools, this server is significantly over the typical well-scoped range. While each tool has a purpose, the proliferation of extraction and generation tools makes the surface feel heavy for an agent to navigate.

    Completeness3/5

    The tool set covers session management, core page interactions, extraction, and auth, but lacks common browser automation actions like hover, keyboard input, and JavaScript evaluation. This leaves notable gaps that agents may need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues