Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceBrowser 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.224 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a real Chromium browser over MCP using genuine mouse, keyboard, and wheel input, with accessibility snapshots, diffs, network logs, forked sessions, and replayable traces for bug bounty hunting.8MIT
- AlicenseBqualityCmaintenanceEnables AI tools to drive a hosted headless Chromium browser over HTTP, allowing LLMs to navigate, click, type, and read web pages through accessibility snapshots.233,465,430 npmApache 2.0
- AlicenseBqualityBmaintenanceA browser automation MCP server that enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or vision models.243,465,430 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to drive a Chromium browser over MCP, reading pages as a numbered list of controls and performing actions like clicking, filling forms, and asserting page state without screenshots or API keys.1076 PyPI20MIT
- AlicenseBqualityCmaintenanceEnables 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.233,465,430 npmApache 2.0
TDQS
Scored across 25 tools
Most tools have clearly distinct browser-automation purposes, but a few boundaries blur: browser_close vs. browser_tabs can both close tabs, and browser_evaluate vs. browser_run_code_unsafe both execute code in different contexts. The descriptions usually clarify these differences, though an agent may still hesitate in edge cases.
All tool names use a consistent browser_ prefix followed by snake_case verbs or noun phrases. The pattern is predictable throughout the set.
25 tools is at the heavy end for a browser automation server; while most operations are genuinely useful, the surface feels granular and borderline overloaded. A more compact set could combine several low-level controls without losing capability.
The surface covers navigation, interaction, forms, screenshots, snapshots, tabs, dialogs, uploads, network/console inspection, and code execution. Minor gaps exist, such as explicit forward navigation/reload and cookie/storage management, but agents can often work around them with evaluate or run_code_unsafe.