cowork-qa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COWORK_QA_DATA | No | Directory where trace files are written | <cwd>/.cowork-qa |
| COWORK_QA_HEADED | No | Set to '1' to launch Chromium with a visible window |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| session_startA | Open a fresh browser tab and start recording a goal-driven session. |
| session_actB | Perform a browser action in a session: goto | click | fill | press | eval. |
| session_observeA | Return the current URL and aria-snapshot of the session's page. |
| session_endA | Close the session, persist the trace to disk, and return the path. |
| qa_get_traceA | Return the full recorded trace (goal, every step, final URL, final aria-snapshot) so the calling LLM can judge whether the goal was achieved. Call session_end first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.