Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- 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,508,652 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,508,652 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables AI assistants to drive a real headless Chromium browser over a hosted HTTP endpoint, navigating, clicking, typing, and reading pages through structured accessibility snapshots rather than screenshots. Runs as a remote service authenticated with a bearer token, so no local browser install or per-machine setup is needed.238,508,652 npmApache 2.0
- 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,508,652 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,508,652 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables AI assistants to control a hosted headless Chromium browser over HTTP via the Model Context Protocol, allowing them to navigate pages, click, type, and read structured accessibility snapshots.238,508,652 npmApache 2.0
TDQS
Scored across 23 tools
Most tools target clearly distinct browser actions, but a few pairs could be confused: browser_type vs browser_fill_form, browser_evaluate vs browser_run_code_unsafe, and browser_drop vs browser_drag. Descriptions do resolve these, but the boundaries require careful reading.
Every tool follows the same browser_<verb> or browser_<noun> snake_case convention with no deviations. The naming is predictable and easy to scan.
23 tools is slightly heavy, but the breadth of browser automation (navigation, forms, network, dialogs, tabs, input) justifies most of them. A few could potentially be consolidated.
The surface covers core browser automation well: navigation, clicking, typing, screenshots, snapshots, network, console, dialogs, tabs, uploads, and waits. Minor gaps exist, such as no forward-navigation tool, no cookie/storage management, and no explicit frame handling.