playwright-mcp-humanized
Related Servers
Alternatives to playwright-mcp-humanized
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceAn MCP server that provides a stealth-enhanced Playwright browser automation engine with anti-detection features, enabling AI agents to navigate websites, interact with elements, and bypass anti-bot systems.241Apache 2.0
- AlicenseBqualityCmaintenanceProvides undetectable browser automation for LLM agents via MCP, enabling real Chrome interaction with stealth features, DOM accessibility, and DevTools integration.983MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser through Playwright tools, allowing web automation tasks such as navigation, clicking, typing, and screenshots.6,282 npm-
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.101-
- FlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to control a browser through Playwright, supporting tasks like navigation, typing, clicking, and taking screenshots.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a web browser using Playwright, supporting navigation, interaction, and data extraction through natural language.MIT
TDQS
Scored across 24 tools
Most tools are clearly distinct (navigate, click, snapshot, screenshot, wait, tabs), but a few pairs could be confused: browser_evaluate vs browser_run_code_unsafe both execute JavaScript, and browser_drag vs browser_drop both describe drag/drop behavior. The descriptions do enough to clarify most boundaries.
All tools share the consistent browser_ prefix and snake_case style, which creates a predictable pattern. Minor deviations exist where some tools are noun-phrases rather than verb commands (browser_network_requests, browser_tabs, browser_snapshot), but these are not disruptive.
At 24 tools, the set is on the heavy side for the border of the recommended range. The domain is broad enough to justify many of them, but there is some redundancy (fill_form vs type, drag vs drop, evaluate vs run_code_unsafe) that makes the count feel slightly inflated.
The set covers the major browser automation lifecycle: navigation, interaction, form filling, waiting, snapshots, screenshots, console/network inspection, dialogs, tabs, and uploads. The main gap is browser forward navigation, and there is no dedicated reload action, but these can be worked around with browser_navigate or browser_run_code_unsafe.