Xiaozhi YouTube MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind host | 0.0.0.0 |
| PORT | No | HTTP port | 3000 |
| MCP_PATH | No | MCP HTTP route | /mcp |
| MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| YOUTUBE_API_KEY | Yes | Google API key for YouTube Data API v3 (required) | |
| YOUTUBE_REGION_CODE | No | ISO two-letter region code | VN |
| YOUTUBE_SAFE_SEARCH | No | SafeSearch setting: none, moderate, or strict | moderate |
| YOUTUBE_CACHE_TTL_SECONDS | No | Cache TTL in seconds for API responses | 300 |
| YOUTUBE_RELEVANCE_LANGUAGE | No | Search relevance language | vi |
| YOUTUBE_DEFAULT_MAX_RESULTS | No | Default number of search results (max 10) | 5 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youtube_search_songA | Search YouTube Music-category videos and return playable YouTube URLs. Use this when the user asks to find or play a song. |
| youtube_play_songB | Find the best matching song and return one playback-ready YouTube URL. Prefer this for direct voice commands such as 'play...' |
| youtube_get_videoB | Get title, channel, duration, views, thumbnail, and playback URL for a YouTube video ID. |
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
Tools are distinct: search returns multiple URLs, play returns one best match, get provides metadata. However, search and play both handle song queries, causing slight overlap, but descriptions clarify their usage.
All tools follow a consistent 'youtube_verb_noun' pattern (search_song, play_song, get_video), using underscores and clear action-object format.
Three tools is appropriate for a focused YouTube music MCP server, covering search, playback, and metadata without unnecessary bloat.
Covers core music workflows: searching songs, playing, and getting video details. Minor gaps like playlist or recommendation support exist but are outside stated scope.