YouTube MCP Server
Related Servers
Alternatives to YouTube MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to pull full transcripts from YouTube videos, search videos and channels, browse a channel's complete upload history, search within a single channel, and extract every video in a playlist through one hosted remote endpoint. It supports API-key or OAuth 2.1 sign-in with no local installation, returning metadata and paginated results with stable error codes.27MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with token-optimized access to YouTube data, including video details, transcripts, channel statistics, trending videos, and search.498 npmMIT
- AlicenseAqualityCmaintenanceProvides production-grade tools for YouTube channel resolution, video metadata extraction, transcripts, and playlist management. It features a quota-aware, AI-friendly design that supports structured searching and listing of public YouTube data.72MIT
- AlicenseAqualityAmaintenanceYouTube transcripts as token-efficient AI context. One fetch, cached. No yt-dlp, no API keys, no system dependencies. ~50 KB per video, instant re-reads from local cache.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables retrieval and analysis of content from YouTube, TikTok, Instagram, and Threads, including metadata, captions, comments, feeds, search results, transcripts, and on-screen text from videos or slides. Supports local stdio and remote HTTP/SSE deployment with optional API keys, Whisper transcription, and Tesseract OCR.MIT
- AlicenseBqualityNot gradedmaintenanceYouTube intelligence layer for AI agents. 41 tools across 10 modules ; search, explore, transcripts, comments, visual search, analytics, and more. Zero config.4177 npm-
TDQS
Scored across 15 tools
Most tools target distinct resource/action pairs, and descriptions actively disambiguate the near-overlaps (get_transcript vs get_timestamped_transcript, get_comments vs get_comment_replies, list_channel_videos vs list_playlist_items). The main soft collision is youtube_get_video vs youtube_get_video_stats, since statistics can be requested via get_video's `parts` — the quota-bucket rationale explains the split but doesn't fully remove the choice ambiguity.
Every tool uses the same `youtube_` prefix followed by a clean verb_noun pattern (get_, list_, search_), all snake_case. Verb choice is predictable and maps to the operation type throughout.
15 tools is well within a healthy range and each one covers a distinct slice of the read surface (metadata, stats, transcripts, comments, playlists, search, quota). Nothing feels padded or redundant enough to warrant pruning.
The read-only domain is broadly covered: channels, videos, stats, comments/replies, playlists, transcripts, categories and quota. Notable gaps remain — there is no way to list a channel's non-uploads playlists or to search for channels directly, so playlist IDs and channel discovery depend on external input or a scarce search call.