MCP yt-dlp 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 |
|---|---|
| download_videoC | Download a video from a URL using yt-dlp. Supports YouTube and many other sites. |
| download_streamB | Download a live stream or m3u8/HLS stream using yt-dlp. |
| get_video_infoB | Get information about a video or stream URL without downloading it. |
| list_formatsA | List all available formats for a video URL. |
| search_videosB | Search for videos using yt-dlp's extractors. |
| update_yt_dlpA | Update yt-dlp to the latest version. |
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 6 tools
Each tool targets a distinct action: updating the tool, downloading videos, downloading streams, fetching metadata, listing formats, and searching. There is no overlap between download_video and download_stream (explicitly split by content type), and get_video_info/list_formats serve separate informational purposes.
All tool names follow a consistent snake_case verb_noun pattern: update, download, get, list, search. The verbs clearly indicate the action and the nouns specify the target, making the convention uniform and predictable.
With 6 tools, the server is well-scoped for a yt-dlp wrapper. Each tool covers a core functionality (update, video download, stream download, info retrieval, format listing, search) without redundancy or bloat, fitting neatly in the typical 3-15 tool range.
The tool set covers the essential lifecycle for video retrieval: searching, inspecting (info/formats), and downloading (video/stream). Minor gaps exist, such as playlist downloads or extracting audio, but agents can likely work around these via download options, so the surface is adequate for most primary workflows.