whipscribe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHIPSCRIBE_API_KEY | No | API key (unlocks paid quota; anonymous free tier works without it) | |
| WHIPSCRIBE_API_BASE | No | Override API base URL (e.g. for staging) | https://whipscribe.com/api/v1 |
| WHIPSCRIBE_MCP_TELEMETRY | No | Set to 0 to disable anonymous usage telemetry | 1 |
| WHIPSCRIBE_MCP_POLL_TIMEOUT_SECONDS | No | Max seconds transcribe_url / transcribe_file waits before returning the job_id with a non-terminal status | 600 |
| WHIPSCRIBE_MCP_POLL_INTERVAL_SECONDS | No | Seconds between job-status polls during transcription | 3 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_urlA | Transcribe audio or video from a URL (direct media link, podcast episode, or Creative-Commons YouTube). Polls until the job is done or the poll timeout elapses, then returns a transcript preview plus a link to the full transcript. |
| transcribe_fileA | Transcribe a local audio or video file. The path is never sent to telemetry. Polls until the job is done or the poll timeout elapses. |
| get_job_statusA | Poll the current status of a transcription job by job_id. |
| get_transcriptA | Fetch a finished transcript in the requested format. Returns a 300-character preview plus a link to the full transcript; large transcripts are not inlined in the MCP response. |
| list_recent_jobsA | List jobs submitted from this machine (local SQLite cache). Stores only job_id, source kind, status, duration, and created-at timestamp — never URLs, file paths, or transcripts. |
| transcribe_urls_batchA | Transcribe a list of URLs (YouTube, podcast, direct media) concurrently. Submit up to 20 URLs in one call; each job runs in parallel and the tool returns when all are done or failed. Per-URL failures do not abort the batch. Ideal for building a second-brain knowledge base from a playlist or a curated list of videos. |
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 targets a distinct action: submitting jobs (file, URL, batch), checking status, fetching transcripts, and listing recent jobs. There is no overlap or ambiguity between tool purposes.
All tool names follow a consistent 'verb_noun' pattern using snake_case (e.g., transcribe_file, get_job_status). The prefixes 'get_', 'list_', and 'transcribe_' are used uniformly.
With 6 tools, the scope is well-scoped for a transcription MCP server. Each tool serves a distinct function without being overly granular or insufficient.
The core workflow of submitting transcription jobs (single file, single URL, batch) and retrieving results is covered. Missing operations like canceling or deleting jobs are minor gaps but not critical for the primary use case.