Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- 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.233,465,430 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables AI tools to remotely control a hosted headless Chromium browser over HTTP to navigate, click, type, and extract structured page content through the Model Context Protocol.233,465,430 npm1Apache 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.233,465,430 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.233,465,430 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.233,465,430 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables an LLM to control a hosted headless Chromium browser over HTTP, navigating pages, clicking, typing, and reading structured accessibility snapshots so any MCP client can perform browser automation without local installation.233,465,430 npmApache 2.0
TDQS
Scored across 23 tools
Most tools map to clearly distinct browser actions like navigate, click, type, hover, select, upload, and screenshot. A few overlapping pairs exist—browser_type vs browser_fill_form and browser_drag vs browser_drop—but the descriptions provide enough boundary to avoid serious misselection.
All tools share a consistent browser_ prefix and snake_case convention, with most following a verb_noun pattern. A few exceptions like browser_network_requests, browser_console_messages, and browser_tabs are noun phrases rather than action-oriented names, creating minor inconsistency.
23 tools is on the heavier side, but the broad scope of browser automation justifies most of them. Each tool covers a distinct capability, though some granularity—such as splitting network_requests and network_request or snapshot and screenshot—feels slightly expansive.
The set covers navigation, interaction, form filling, file uploads, waiting, screenshots, accessibility snapshots, network inspection, console messages, dialogs, tabs, and JavaScript evaluation. Minor gaps like browser_forward, cookie management, or local storage handling exist, but most browser workflows can be completed without them.