mcp-playwright-automation
Related Servers
Alternatives to mcp-playwright-automation
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to perform browser automation using Playwright, including navigation, content extraction, screenshot analysis, and custom script execution.531 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser through Playwright tools, allowing web automation tasks such as navigation, clicking, typing, and screenshots.6,893 npm-
- FlicenseNot gradedqualityFmaintenanceEnables AI assistants to control a browser through Playwright tools for web automation tasks like navigation, typing, clicking, and taking screenshots.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to automate web browsers through Playwright, providing capabilities for navigation, content extraction, form filling, screenshot capture, and JavaScript execution. Supports multiple browser engines with comprehensive error handling and security features.1-
- AlicenseNot gradedqualityDmaintenanceEnables browser automation for AI assistants via Playwright, supporting multiple browsers, sessions, and tools for web interaction and testing.1,029 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a web browser using Playwright, supporting navigation, interaction, and data extraction through natural language.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct browser action: navigation, clicking, form filling, data extraction, content retrieval, and screenshots. No overlap in purpose, so agents can clearly differentiate.
Naming mixes conventions: snake_case verbs (navigate, click, screenshot) and camelCase verb_noun (fillForm, extractData, getPageContent). The pattern is inconsistent, with some tools using single verbs and others using verb_noun, and differing case styles.
Six tools form a tight, well-scoped set for basic browser automation, each earning its place. This is within the ideal 3-15 range.
The surface covers core browsing workflows (navigate, interact, extract, screenshot) but lacks common operations like waiting for elements, hovering, selecting options, or scrolling. Basic tasks are possible, but advanced automation scenarios would require workarounds.