YouTube MCP Server
Related Servers
Alternatives to YouTube MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.15MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with token-optimized access to YouTube data, including video details, transcripts, channel statistics, trending videos, and search.423 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.21MIT
- AlicenseBqualityNot gradedmaintenanceYouTube intelligence layer for AI agents. 41 tools across 10 modules ; search, explore, transcripts, comments, visual search, analytics, and more. Zero config.41189 npm-
- AlicenseBqualityBmaintenanceEnables AI agents to fetch the transcript, description, and comments of any YouTube video so they can read, summarize, and analyze video content. It ships a four-layer anti-blocking fallback cascade and disk caching for reliable, low-cost retrieval without API keys.4MIT
TDQS
Scored across 11 tools
Each tool has a distinct focus (transcript text vs. timed segments vs. language listing vs. in-transcript search vs. general video search vs. metadata vs. stats vs. comments vs. channel vs. channel uploads vs. categories). The main potential confusion is between youtube_get_transcript and youtube_get_timestamped_transcript, but the descriptions clarify exactly when to use each.
All 11 tools follow a strict youtube_verb_noun pattern (e.g., youtube_get_transcript, youtube_search_videos, youtube_list_channel_videos, youtube_get_video_stats). No deviations in casing or verb style.
With 11 tools, the set is well-scoped: it covers transcripts, searches, video metadata, stats, comments, channels, and categories without being bloated or thin. Each tool earns its place and no obvious overlaps require merging.
The surface covers most read-only YouTube operations, including transcript access, video/channel data, comments, and search. Primary gaps are write operations (e.g., posting comments) and replies in comments, but these may be intentional for a read-only server; the core discovery and retrieval workflows are complete.