YouTube Transcript MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transcriptA | Fetch the transcript for a YouTube video. Args: video_url_or_id: YouTube video URL or video ID languages: List of language codes to try (e.g., ['en', 'es']). If None, uses default. format_type: Output format - 'text' or 'json' ctx: MCP context for logging |
| get_available_languagesA | Get available transcript languages for a YouTube video. Args: video_url_or_id: YouTube video URL or video ID ctx: MCP context for logging |
| search_transcriptA | Search for specific text within a YouTube video's transcript. Args: video_url_or_id: YouTube video URL or video ID query: Text to search for in the transcript languages: List of language codes to search in. If None, uses default. ctx: MCP context for logging |
| get_transcript_summaryA | Get a summary of a YouTube video's transcript. Args: video_url_or_id: YouTube video URL or video ID max_length: Maximum length of the summary in characters languages: List of language codes to use. If None, uses default. ctx: MCP context for logging |
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 4 tools
Each tool has a clearly distinct purpose: fetching full transcripts, listing available languages, searching within a transcript, and summarizing a transcript. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (get_transcript, get_available_languages, search_transcript, get_transcript_summary). The verbs vary appropriately based on action, but the naming convention is uniform and predictable.
With only 4 tools, the server is tightly scoped to transcript-related operations. Each tool serves a distinct and necessary function for the domain, making the count appropriate and well-balanced.
The tool set covers the core transcript workflow: retrieval, language discovery, searching, and summarization. There are no obvious dead ends or missing operations for a transcript-focused MCP server.