Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables any MCP client to drive a hosted headless Chromium browser over HTTPS — navigating, clicking, typing, and reading pages via structured accessibility snapshots — with no local browser install or npx required. It runs as a single Render web service behind a bearer-token gate, since upstream ships no authentication of its own.23Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI tools to drive a hosted, headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots — without installing a browser locally or running npx on each machine. It runs as a single authenticated Render web service that any MCP client can connect to at a shared HTTPS endpoint.23Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI assistants and MCP clients to drive a hosted headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages via structured accessibility snapshots rather than screenshots. Runs as a Render web service behind a bearer-token gate, so no local browser install or npx setup is required on each machine.23Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI clients to drive a hosted headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots rather than screenshots. Runs as a single authenticated web service, so any MCP client can connect to a shared HTTPS URL without installing a local browser.23Apache 2.0
- AlicenseBqualityCmaintenanceEnables LLMs and MCP clients to control a hosted headless Chromium browser over HTTP, navigating, clicking, typing, and reading pages via structured accessibility snapshots, with bearer-token authentication.23Apache 2.0
- AlicenseBqualityCmaintenanceDeploys a hosted, authenticated MCP server that lets AI assistants drive a real headless browser over HTTP, enabling navigation, clicking, typing, and reading pages without local browser setup.2310,908,336 npmApache 2.0
TDQS
Scored across 23 tools
Most tools target clearly distinct browser actions, and descriptions explicitly separate potential confusions like browser_snapshot vs browser_take_screenshot and browser_evaluate vs browser_run_code_unsafe. Some minor overlap exists among browser_type, browser_fill_form, and browser_press_key, but each remains reasonably distinguishable.
All tools follow a consistent browser_ snake_case prefix with predictable action-oriented names. Occasional noun-style names like browser_console_messages still fit the uniform convention.
At 23 tools, the set sits in the heavy 16-25 range and could feel overwhelming for an agent. Most tools are legitimately needed for comprehensive browser automation, but the count is borderline rather than well-scoped.
The surface covers core browser automation needs: navigation, interaction, evaluation, network inspection, console messages, screenshots, tabs, dialogs, file upload, drag/drop, and waits. Minor gaps remain, such as explicit forward/reload navigation, cookie/storage management, and download handling.