Skip to main content
Glama
Sign In
DailyNoBug

Playwright Browser MCP Server

by DailyNoBug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Playwright Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • MultiZen

      nerea71972
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents and human operators drive isolated Chromium profiles with their own cookies, fingerprints, and proxies, exposing tools for navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits. Because session and login state persist per profile, agents can carry out real authenticated workflows across sessions.
      MIT

    • Bosun

      The-Glassy
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP browser service that lets AI agents drive a real headful Chromium, patchright, or camoufox session — navigating, reading accessibility snapshots, clicking, typing, and taking screenshots — with scheduled keepalive visits and Google Meet notetaking. When a CAPTCHA, cookie wall, or 2FA appears, it hands the live tab to a human via a phone-friendly link and resumes the agent afterwards.
      Apache 2.0

    • Pilot

      TacosyHorchata
      A
      license
      A
      quality
      C
      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
      20 npm
      32
      MIT

    • CloakBrowser MCP

      ryotali0703
      A
      license
      Not graded
      quality
      A
      maintenance
      This server enables MCP clients and AI agents to perform browser automation with Playwright-compatible tools, persistent profiles, extensions, proxy support, and humanized interactions. It can be run via npm or Docker over stdio or Streamable HTTP for web research, automation, testing, and regional QA.
      541 npm
      MIT

    • relaywright

      JiangnanZhang-2006
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to learn a Chromium browser task once and then replay it deterministically without spending LLM tokens, handing off logins and CAPTCHAs to a human while keeping credentials out of the model. Every step is de-identified for privacy and written to a hash-chained audit log, available as both an MCP server and a CLI.
      Apache 2.0

    • byob

      Pavelj43
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.
      1 npm
      ISC
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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

    Resources