Playwright Automation MCP Server
Related Servers
Alternatives to Playwright Automation MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceProvides browser automation tools for AI assistants via the Model Context Protocol, enabling tasks like navigation, clicking, filling forms, screenshots, and script execution through natural language.39-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a web browser using Playwright, supporting navigation, interaction, and data extraction through natural language.MIT
- AlicenseAqualityAmaintenanceEnables browser automation through the Model Context Protocol, allowing AI agents to control Chrome, Firefox, or Edge for tasks like navigation, clicking, typing, and screenshots.4140 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser through Playwright tools, allowing web automation tasks such as navigation, clicking, typing, and screenshots.4,799 npm-
- FlicenseNot gradedqualityCmaintenanceEnables browser automation and testing using Playwright through the Model Context Protocol.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate web tasks such as browsing, clicking, typing, and taking screenshots via the Model Context Protocol.1MIT
TDQS
Scored across 10 tools
Each tool targets a distinct action: navigation, login, registration, product browsing, cart management, screenshot, logout, and browser cleanup. No two tools appear to do the same thing, even though click_continue is narrow but clearly tied to the registration flow.
All tools use snake_case with a clear verb-first pattern (e.g., login_user, browse_products, add_product_to_cart). Naming is highly consistent and predictable, with no camelCase or mixing of conventions.
Ten tools is a well-scoped set for automating a specific website's user flows. Each tool serves a concrete purpose in the main journey (navigate, register, login, browse, cart, logout), with no bloat or unnecessary duplication.
The tool set covers the core lifecycle of a user on AutomationExercise: registration, login, browsing, adding to cart, viewing cart, and logout. Minor gaps exist, such as no checkout, cart removal, or product detail retrieval, but these are not critical for the apparent automation purpose.