cowork-qa-mcp
Related Servers
Alternatives to cowork-qa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables agents to control a real Chromium browser with semantic tools, providing compact observations and outcome-verified actions for web interaction tasks.1MIT
- AlicenseAqualityAmaintenanceProvides browser automation tools for coding agents—goto, browse, goal, page_state, and summary—so agents can drive real pages through auditable, gated decisions and record traces for offline replay.12331Apache 2.0
- FlicenseNot gradedqualityDmaintenanceDrives a real Chromium browser with Playwright, providing a live, clickable view of the page for the model to browse and the user to interact with.2-
- AlicenseAqualityBmaintenanceEnables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.2MIT
- AlicenseBqualityCmaintenanceEnables LLMs to drive a hosted headless Chromium browser over HTTP, performing navigation, clicks, typing, and page reading through accessibility snapshots, protected by bearer-token authentication.237,629,601 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment10162 npm299MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct phase of the session lifecycle (start, act, observe, end, retrieve trace), leaving no ambiguity about which tool to use. The purposes are clearly separated and non-overlapping.
Four of five tools follow a consistent session_<verb> pattern (start, act, observe, end), but qa_get_trace breaks this with a qa_ prefix and a different verb style. The deviation is minor and the intent remains clear.
The tool count of 5 is well-suited for a QA automation server, covering the essential workflow without superfluous or redundant tools. Each tool earns its place in the session lifecycle.
The tool set provides full lifecycle coverage from session start through actions, observation, ending, and trace retrieval. There are no obvious gaps for the intended goal-driven QA workflow.