cowork-qa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COWORK_QA_DATA | No | Directory where <session-id>.json traces are written | <cwd>/.cowork-qa |
| COWORK_QA_HEADED | No | Set to 1 to launch Chromium with a visible window | unset (headless) |
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 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.
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.
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.
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.