Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with web pages through structured accessibility snapshots using Playwright, providing fast and lightweight browser automation without needing vision models.Apache 2.0
- AlicenseBqualityBmaintenanceEnables LLMs to automate browsers and interact with web pages through structured accessibility snapshots, avoiding the need for screenshots or vision-tuned models.25Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to automate browsers and interact with web pages using structured accessibility snapshots rather than screenshots or vision models.Apache 2.0
- AlicenseBqualityCmaintenanceEnables LLMs to control browsers and interact with web pages via structured accessibility snapshots, without needing screenshots or vision models.2410,908,336 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables LLMs to automate web browsers through structured accessibility snapshots, bypassing screenshots and vision-tuned models for deterministic page interaction.2510,908,336 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to automate and interact with web pages via structured accessibility snapshots, bypassing screenshots and vision models.10,908,336 npmApache 2.0
TDQS
Scored across 24 tools
Each tool targets a distinct browser action or resource. Overlapping operations like browser_type vs browser_fill_form are clearly differentiated by scope (single element vs multiple fields), and browser_snapshot vs browser_take_screenshot explicitly separate accessibility tree captures from visual screenshots. No two tools present meaningful ambiguity.
All tools share the 'browser_' prefix followed by a clear verb or verb phrase, using consistent snake_case throughout (e.g., browser_navigate, browser_fill_form, browser_network_request). Even multi-word names like browser_run_code_unsafe remain readable and predictable.
24 tools is above the typical 15-tool sweet spot, but the browser automation domain requires diverse actions including navigation, interaction, network inspection, dialogs, and tab management. Each tool earns its place, and the count feels slightly heavy but justified rather than bloated.
The tool set covers core browser workflows: navigate, interact (click/type/hover/select/drag/drop), wait, snapshot/screenshot, evaluate, handle dialogs, file upload, and network/console inspection. A few minor gaps exist, such as no explicit 'browser_forward' or 'browser_reload', but these can be worked around via navigation or evaluation.