YouTube MCP
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 |
|---|---|
| youtube_auth_statusA | Check whether local YouTube OAuth credentials and token are available. |
| youtube_auth_urlA | Create a Google OAuth URL using the local desktop app client secret. |
| youtube_auth_exchange_codeB | Exchange a pasted OAuth authorization code for a local token file. |
| youtube_search_videosC | Search public YouTube videos with YouTube Data API v3. |
| youtube_get_videoC | Get snippet, statistics, and content details for a video. |
| youtube_get_channelC | Get snippet, statistics, and content details for a channel. |
| youtube_list_my_videosC | List videos from the authenticated channel uploads playlist. |
| youtube_get_video_analyticsC | Read analytics metrics for one authenticated-channel video. |
| youtube_get_channel_analyticsC | Read channel analytics metrics for the authenticated channel. |
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 9 tools
Each tool has a distinct purpose: three for OAuth, two for channel data (with analytics), two for video data (with analytics), one for listing own videos, and one for public search. No overlap in functionality.
All tools are prefixed with 'youtube_' and mostly follow a verb_resource pattern (e.g., get_channel, search_videos). However, auth tools use a resource_verb pattern (auth_exchange_code) and there is a mix of 'get_' and 'list_' for retrieval, causing minor inconsistency.
With 9 tools, the server covers authentication, channel info, video info, analytics, and search without being overly large or small. The number is well-suited for a focused YouTube data and analytics MCP server.
The server provides read and analytics operations but lacks write capabilities (e.g., upload, update, delete videos) and playlist management. For a server named 'YouTube MCP', these are notable gaps, making it incomplete for full channel management.