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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-transcriptA | Retrieve the transcript of a YouTube video. Accepts various YouTube URL formats and returns the full transcript with timestamps. |
| get-transcript-languagesA | List all available transcript languages for a YouTube video. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a transcript, the other lists available languages. No overlap or confusion possible.
Both tools follow a consistent 'get-{noun}' pattern, making the naming predictable and easy to understand.
With only 2 tools, the server feels thin for its domain. While it covers the core need, a typical well-scoped server has more tools.
The server provides basic transcript retrieval and language listing, but lacks operations like searching transcripts or filtering by language, leaving minor gaps.