ClipQA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIPQA_DATA_DIR | No | Directory where sessions are stored. Defaults to ~/.clipqa/sessions. | ~/.clipqa/sessions |
| CLIPQA_FFMPEG_PATH | No | Path to the FFmpeg binary. Overrides the bundled FFmpeg binary. | |
| CLIPQA_FFPROBE_PATH | No | Path to the FFprobe binary. Overrides the bundled FFprobe binary. |
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 |
|---|---|
| list_windowsA | List visible Windows application windows that can be recorded. Read-only. |
| start_recordingC | Start quiet background recording of one Windows application window. This does not control input or capture audio. |
| mark_eventC | Add a timestamped action, assertion, error, or note to an active QA recording. |
| stop_recordingC | Stop a recording gracefully and finalize the clip. |
| list_sessionsB | List recorded QA sessions and their status. |
| inspect_clipB | Create and return a timestamped contact sheet for a completed recording. |
| get_framesB | Return full-size frames from exact timestamps in a completed recording. |
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 7 tools
Each tool maps to a distinct stage of the recording workflow—discover, start/stop, annotate, list, inspect frames—so selection is generally clear. The only mild overlap is between inspect_clip and get_frames, which both retrieve visual data from a completed recording, but their descriptions clarify the different output forms.
All tool names use a consistent snake_case verb_noun pattern (list_windows, start_recording, stop_recording, mark_event, list_sessions, inspect_clip, get_frames). There are no irregular verbs, abbreviations, or mixed casing to confuse an agent.
Seven tools is right-sized for this server's purpose: a focused QA clip recording and inspection workflow. Each tool represents a necessary operation with no redundant helpers or bloat.
The core lifecycle is covered: discover windows, start/stop recording, mark events, list completed sessions, and inspect clips via contact sheets or exact frames. The main gaps are housekeeping and retrieval—there is no delete/cleanup session tool and no way to fetch the raw clip file itself, though these may be outside the server's designed scope.