yt-media-info-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Winston log level (error, warn, info, debug) | info |
| ENABLE_SSE | No | Use SSE transport (vs stdio) | 0 |
| YT_MEDIA_INFO_HOST | No | HTTP server host (SSE mode) | 0.0.0.0 |
| YT_MEDIA_INFO_PORT | No | HTTP server port (SSE mode) | 9423 |
| YT_MEDIA_INFO_API_KEY | No | Optional bearer API key for HTTP endpoints | |
| YT_MEDIA_INFO_PASSWORD | No | Default password for yt-dlp site auth | |
| YT_MEDIA_INFO_USERNAME | No | Default username for yt-dlp site auth | |
| YT_MEDIA_INFO_SERVICE_URL | No | URL of the Python yt-dlp service | http://yt-media-info-service:8000 |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_infoA | Extract rich metadata from a media URL (title, description, duration, formats, chapters, subtitles, statistics, and more) |
| get_transcriptB | Fetch subtitles or transcript text for a media URL, optionally with timestamp segments |
| search_mediaA | Search for media across supported platforms (YouTube, etc.) using yt-dlp search. This is a supplementary discovery tool meant to complement web search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_video | Analyze a video or media item from its available metadata to provide insights, context, and high-level understanding |
| summarize_transcript | Summarize the transcript of a video or audio file to extract key points and actionable insights |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: metadata extraction, transcript retrieval, and media search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (extract_info, get_transcript, search_media) using lowercase snake_case.
Three tools is appropriate for a focused media info server, covering core operations without excess.
The tool set covers the main use cases for media information: metadata extraction, transcript fetching, and search. No obvious gaps for its stated purpose.