A
licenseNot graded
qualityNot graded
maintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.
3,661 npm
57
-
cowork-qa-mcp
by Cultistsid
Related Servers
Alternatives to cowork-qa-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides browser automation using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots.-
- AlicenseBqualityBmaintenanceA browser-automation MCP server built on Playwright that provides deterministic snapshots via MutationObserver/requestAnimationFrame, HITL governance, multi-task isolation, and self-healing browser sessions for LLM-driven browsing.25MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.4,799 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.6 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive a browser and record every action into a replayable trace, then replay it deterministically with network request assertions. It exposes tools for navigating, clicking, filling, and verifying requests.-
TDQS
A3.6/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct phase of the session lifecycle: start, act, observe, end, and trace retrieval. There is no overlap in purpose, and the descriptions clearly delineate which tool to use at each point in a workflow.
Naming Consistency4/5
The session_* tools follow a consistent verb_noun pattern (session_start, session_act, session_observe, session_end). qa_get_trace is a minor deviation from the prefix convention, though it's clearly thematic and still readable.
Tool Count5/5
Five tools is well-scoped for a QA session recorder. Each tool earns its place: lifecycle management (start/end), actions (act), observation (observe), and trace retrieval (qa_get_trace). No redundancy or unnecessary tools.
Completeness5/5
The surface covers the full session lifecycle: start a session, perform actions, observe state, end the session, and retrieve the trace for evaluation. There are no dead ends—qa_get_trace even instructs the caller to call session_end first, closing the loop.
Maintenance
ActivityInactive
ResponsivenessNo issues