sa2web-mcp
Related Servers
Alternatives to sa2web-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.-

orchords-web-pilotofficial
FlicenseAqualityBmaintenanceEnables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.152-- AlicenseAqualityBmaintenanceEnables AI agents to drive a real Playwright browser over MCP to navigate pages, read accessibility-tree snapshots, click, type, screenshot, and evaluate JavaScript, either in a managed browser or attached to a running Chromium-based browser via CDP.201MIT
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.4101-
- AlicenseNot gradedqualityDmaintenanceEnables browser automation and web scraping by exposing Playwright tools through an HTTP-based MCP server. Users can navigate pages, interact with web elements, capture screenshots, and extract structured content using a persistent Chromium instance.MIT
- FlicenseNot gradedqualityCmaintenanceEnables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.-
TDQS
Scored across 19 tools
The set contains two identical screenshot tools (browser_screenshot and browser_take_screenshot), creating direct ambiguity. Several other tools overlap in edge behavior (browser_paste/browser_file_upload, browser_toggle_device/browser_resize), and browser_navigate references a sa2_open_target tool not present in the set, making selection confusing.
Tool names consistently use a browser_ prefix with snake_case verbs, which makes the overall pattern predictable. The main inconsistency is browser_screenshot versus browser_take_screenshot, where two names exist for the same action, plus the odd browser_open_login compatibility naming.
19 tools is on the heavy side for a browser utility surface, especially given a duplicate screenshot tool and advanced compatibility aliases. It is not excessive enough to be unusable, but several tools feel redundant, so the count is not well-trimmed.
Fundamental browser interactions are missing: there is no general click, text extraction, wait, or hover tool, and browser_run_code is the only fallback for basic actions. The descriptions also recommend sa2_open_target as the preferred entry point, but that tool is absent from the set, creating a dead end.