Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceLets AI clients drive a real headless Chromium browser through a hosted HTTPS endpoint — navigating, clicking, typing, and reading pages via structured accessibility snapshots rather than screenshots. Requests are gated behind a bearer token, so no local browser install or npx is needed on each machine.238,572,341 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables AI tools to drive a hosted headless Chromium browser over HTTP for navigation, clicking, typing, and reading pages via structured accessibility snapshots, without local browser installs.238,572,341 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables AI tools to drive a hosted headless-Chromium browser over HTTP, letting them navigate, click, type, and read web pages through accessibility snapshots.238,572,341 npmApache 2.0
- 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.238,572,341 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables 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.238,572,341 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants to drive a hosted headless Chromium browser over HTTP, letting them navigate pages, click, type, and read structured accessibility snapshots via the Model Context Protocol.238,572,341 npmApache 2.0
TDQS
Scored across 23 tools
Tools are mostly distinct with clear action-based descriptions; overlaps like screenshot/snapshot and network_requests/network_request are explicitly differentiated. A few pairs (evaluate vs run_code_unsafe, drop vs drag, close vs tabs-close) could still cause hesitation but are manageable.
All tools use a consistent browser_ prefix and snake_case. Minor deviations exist (plural vs singular for network requests, verb vs noun phrasing), but the pattern is predictable.
23 tools is on the heavy side for the 3-15 ideal range, but each tool maps to a distinct browser action. The count is borderline but justified by the breadth of browser automation.
Covers navigation, interaction, forms, dialogs, network, console, screenshots, and tabs comprehensively. Missing forward navigation and reload are minor gaps that agents can work around via evaluate or navigate.