A
licenseNot graded
qualityA
maintenanceEnables agents to control a real Chromium browser with semantic tools, providing compact observations and outcome-verified actions for web interaction tasks.
1
MIT
cowork-qa-mcp
Related Servers
Alternatives to cowork-qa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- 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.3320 PyPI2Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that provides an LLM with a real Chromium browser via Playwright, recording every action taken toward a stated goal and producing a structured trace so the run can be audited for goal achievement.544 npmMIT
- 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-
- AlicenseAqualityAmaintenanceEnables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.2MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness5/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues