youtube-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Bind port, http only. | 8000 |
| MCP_HOST | No | Bind address, http only. | 127.0.0.1 |
| MCP_TRANSPORT | No | Transport: 'stdio' or 'http'. | stdio |
| PUBLIC_BASE_URL | No | Where the server is reachable, used for the icon URL. | |
| YOUTUBE_PROXY_URL | No | Proxy endpoint, credentials included. | |
| YOUTUBE_USE_PROXY | No | The switch that turns the proxy on. | false |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youtube_transcriptA | Read what is said in a YouTube video, as plain text. You get the whole thing by default. On a long video, narrow it with start_seconds and end_seconds so the response stays small. A caption line that straddles either edge of that window comes back whole rather than cut in half. English is preferred, then a handful of widely spoken languages, and failing all of those whatever the video actually has. Check the language field on the way out and translate if you need to. The auto_generated field tells you whether a human wrote the captions or speech recognition did, which is worth knowing before you quote them. The text has no timestamps in it. Shorts are not supported. If you only need the title, length or view count, youtube_video_facts is much cheaper. |
| youtube_playlistA | List the videos in a YouTube playlist, in playlist order. Returns watch URLs and the playlist title, nothing about the videos themselves. Use it to unpack a playlist, then call youtube_video_facts or youtube_transcript on the URLs you get back. A watch link that happens to be playing inside a playlist works here too. |
| youtube_video_factsA | Look up a YouTube video without reading its captions. Gives you the title, channel, duration, publish date, view and like counts, the description, and which caption languages exist. Far cheaper than pulling a transcript, so start here when the question is about the video rather than its contents, or to check a video has captions before asking for them. |
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
Each tool has a clearly distinct purpose: transcript extracts spoken content, playlist lists videos in a playlist, and video_facts provides metadata. There is no overlap or ambiguity between them.
All tool names follow the same pattern: 'youtube_' prefix followed by a descriptive noun or noun phrase. The naming is consistent and predictable, using lowercase with underscores throughout.
Three tools is a reasonable and well-scoped count for a YouTube-focused MCP server. Each tool covers a core, distinct capability without unnecessary bloat, falling within the typical 3-15 range.
The tool set covers the main YouTube interaction needs: reading transcripts, fetching video metadata, and enumerating playlists. Minor gaps exist (e.g., no search or comment retrieval), but the core workflows are complete and work well together.