Playwright MCP Server
OfficialRelated Servers
Alternatives to Playwright MCP Server
AlicenseAqualityAmaintenanceBrowser automation that bypasses anti-bot systems and handles web-scraping with CDP Mode.19224363,481 PyPI13,080MIT
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 gradedqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or vision models.Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or vision models.226,403,349 npm1Apache 2.0
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or visually-tuned models.226,403,349 npmApache 2.0
TDQS
Scored across 25 tools
Most tools target clear, distinct operations (navigate, click, type, hover, drag, screenshot, snapshot), and the pair browser_network_requests/browser_network_request is explicitly cross-referenced. Some overlap exists between snapshot/find/take_screenshot and between type/fill_form/press_key, but descriptions provide adequate guidance.
Every tool follows a strict browser_<action> snake_case convention (browser_navigate, browser_click, browser_take_screenshot, browser_wait_for), making the pattern fully predictable across all 25 tools.
25 tools is at the upper boundary of the ideal range and the surface is broad (tabs, dialogs, media emulation, uploads, network inspection, unsafe code execution). It is defensible for a full browser automation server, but the count feels heavy and encourages selection mistakes.
The surface covers navigation, interaction, snapshots, forms, uploads, drag-and-drop, dialogs, console, network, and media emulation with no obvious dead ends for browser automation workflows.