quickcast-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_sessionB | Retrieve metadata, duration, markers, and Cloudflare R2 watch URL of the latest or specified QuickCast recording session. |
| list_recent_sessionsB | List recent QuickCast screen recording sessions with IDs, timestamps, durations, and shareable watch URLs. |
| format_github_bug_reportB | Format an automated, high-fidelity GitHub/Jira bug reproduction issue markdown document with timestamped video links, environment tables, and failure points from a QuickCast session. |
| scaffold_playwright_testA | Generate an executable Playwright (TypeScript or JavaScript) E2E reproduction test based on the interactions, clicks, and URLs captured during the QuickCast recording. |
| generate_sop_guideB | Generate a clean, structured Standard Operating Procedure (SOP) or training walkthrough document with timestamped video checkpoints from a QuickCast session. |
| ingest_sessionB | Ingest and store a QuickCast recording session into the local session storage (~/.quickcast/sessions.json) so AI assistants can reference it. |
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 6 tools
Each tool has a distinct purpose: listing vs. retrieving session metadata, ingesting, and three different output-artifact generators (SOP, bug report, Playwright test). The only mild overlap is between get_latest_session and list_recent_sessions, but their descriptions clarify the distinction well.
All six tools follow a consistent snake_case verb_noun pattern (generate_sop_guide, list_recent_sessions, get_latest_session, format_github_bug_report, scaffold_playwright_test, ingest_session). The verbs vary appropriately to match each action without breaking the predictable convention.
Six tools is a well-scoped set for a session-recording processing server, covering retrieval, ingestion, and three distinct artifact generators without redundancy or padding.
The surface covers ingestion, listing, retrieval, and several generation workflows, which fits the domain well. Minor gaps remain, such as no delete/update or search-by-content operation, but agents can work around these.