Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to remotely drive a hosted headless browser over HTTP, supporting navigation, clicking, typing, and structured page reading through the Model Context Protocol. It also provides bearer-token authentication for secure remote MCP access.2310,507,590 npmApache 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.2310,507,590 npmApache 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.2310,507,590 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.1523 npm3MIT
- 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.2310,507,590 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.Apache 2.0
TDQS
Scored across 23 tools
Each tool maps to a distinct browser action or state source, and the descriptions generally make boundaries clear. The only mild friction is between browser_type, browser_fill_form, and browser_evaluate, but their usage contexts differ enough to avoid serious misselection.
All tools share a consistent browser_ prefix and snake_case style, which gives the set a predictable feel. A few noun-style tools like browser_tabs, browser_console_messages, and browser_network_requests break the otherwise dominant action-focused pattern, but the deviation is minor.
At 23 tools, the surface feels heavy and sits in the 16-25 range that reads as over-scoped. The browser-automation domain is broad enough that most tools justify their existence, but some consolidation might improve the set's overall tightness.
The surface covers the major browser workflow: navigation, interaction, form filling, waiting, screenshots, snapshots, console/network inspection, dialogs, tabs, and file upload. Minor gaps like reload, forward navigation, and cookie/storage management remain, but agents can work around them with navigate or browser_evaluate.