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 |
|---|---|
| fetch_youtube_transcriptB | Tool to fetch the transcript of a YouTube video. :param video_id: The unique identifier of the YouTube video. :param lang_code: The language code for the transcript (default is 'en' for English). :param format: The desired output format of the transcript; either 'text' or 'json'. :return: The transcript in the specified format. |
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 1 tool
Only one tool exists, so there is no risk of confusion between tools. The tool's purpose is clearly defined.
With a single tool, naming consistency is inherent. The name 'fetch_youtube_transcript' uses clear snake_case and is descriptive.
A single tool for fetching YouTube transcripts is appropriate for a focused service, but the tool surface is minimal and may be considered thin for broader use cases.
The tool covers the primary function of fetching transcripts with language and format options. No additional operations like listing or searching are expected for a transcript-only server, so gaps are minor.