Playwright MCP
Related Servers
Alternatives to Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.236,555,401 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.236,555,401 npmApache 2.0
- 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.236,555,401 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.236,555,401 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.236,555,401 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.236,555,401 npmApache 2.0
TDQS
Scored across 23 tools
Most tools target distinct browser actions (click, type, hover, drag, drop, etc.), and descriptions clarify edge cases like snapshot vs screenshot. However, browser_drag vs browser_drop and browser_type vs browser_press_key could still cause occasional misselection without careful reading.
All tools share a consistent browser_ prefix and snake_case style, but the action part is mixed: verbs (browser_close, browser_evaluate) coexist with nouns (browser_snapshot, browser_network_requests, browser_tabs). This is readable but not a uniform verb_noun pattern.
23 tools is on the heavier side but justified for a full-featured browser automation server covering navigation, input, inspection, network, tabs, and dialogs. A few tools like browser_network_requests/request could arguably be merged, but the count is not excessive.
The toolset covers most core browser automation workflows, including navigation, clicking, typing, forms, screenshots, and network inspection. Minor gaps like dedicated checkbox/radio interaction or page reload are missing, but agents can work around them via browser_click or browser_evaluate.