Capslane YouTube transcript MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPSLANE_API_KEY | Yes | Capslane workspace API key. Required for authentication. Create a key in API Keys and supply it through your environment or secret manager. | |
| CAPSLANE_BASE_URL | No | Optional base URL for the local stdio server. Keep the production URL unless deliberately testing a separate server. |
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 |
|---|---|
| get_youtube_transcriptA | Retrieve captions or generate a transcript for a public YouTube video. Each submission consumes a transcript unit, including cache hits. Can create a generation job. For summaries, notes or timestamp citations, retrieve the transcript first; this tool does not summarize. |
| get_transcript_statusA | Check the same accepted job without consuming another transcript unit. Content means success; stop on failed, cancelled or completed without content (stored result unavailable or expired). A successful tool call can still describe a pending or failed job. Poll with a delay and deadline, never by resubmitting the video. |
| list_available_languagesA | Return languages observed by a native transcript request. Consumes one transcript unit and can populate the cache; it is not a free metadata lookup. Never starts generation. A cached result can have a generated source. |
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 3 tools
The three tools have largely distinct purposes: fetching content, polling job status, and listing languages. However, get_youtube_transcript and list_available_languages both consume transcript units and populate the cache, creating mild ambiguity about when to use one versus the other.
All three tools follow a clean verb_noun snake_case pattern (get_youtube_transcript, get_transcript_status, list_available_languages). Names are predictable and readable.
Three tools for a narrowly scoped transcript-retrieval service is reasonable and each earns its place. It leans slightly thin, with no bulk or batch operation, but the domain doesn't demand more.
The surface covers the core lifecycle: retrieve transcript, poll async job status, and list available languages. Minor gaps exist (e.g., no explicit cancel/delete job operation, despite the status tool referencing cancelled jobs), but agents can work around these.