@playwright/mcp
Related Servers
Alternatives to @playwright/mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually tuned models.717,093 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually-tuned models.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities by allowing LLMs to interact with web pages through structured accessibility snapshots. It enables fast, lightweight interaction with web content without the need for vision-tuned models or visual processing.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for lightweight browser automation using Lightpanda with Chrome fallback, providing LLM-optimized accessibility tree snapshots for precise element targeting.2MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides browser automation capabilities, enabling LLMs to control a web browser for navigation, interaction, and data extraction.32130 npm14MIT

Playwright MCP Serverofficial
AlicenseBqualityAmaintenanceA Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.14256,403,349 npm38,212Apache 2.0
TDQS
Scored across 23 tools
Each tool has a clearly distinct purpose. Overlapping operations like browser_snapshot and browser_take_screenshot are explicitly differentiated in descriptions. No two tools cause ambiguity.
All tools follow a consistent 'browser_verb_noun' pattern (e.g., browser_click, browser_navigate_back, browser_file_upload). The naming is predictable and uniform.
23 tools cover a wide range of browser automation operations without being excessive. The count is appropriate for the domain, though slightly on the higher side.
The tool set covers most essential browser interactions: navigation, clicking, typing, forms, screenshots, dialogs, tabs, network requests, and more. Minor gaps exist (e.g., cookie management, scrolling), but the surface is comprehensive.