YouTube MCP
Related Servers
Alternatives to YouTube MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with YouTube channels, providing analytics, video metadata updates, transcript extraction, and comment management through official Google APIs with OAuth 2.0.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to fetch YouTube video transcripts and metadata without sign-in, and access signed-in users' own YouTube account data such as subscriptions, playlists, uploads, and caption tracks via OAuth 2.0.1323 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage YouTube channels directly, including video publishing, SEO optimization, playlist curation, community interaction, and traffic analytics, all through local OAuth.2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read transcripts of any public video, research channels, analyze performance, read comments, and manage multiple owned channels.1674 npm1MIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to read a creator's own channel analytics, audience and traffic breakdowns, retention curves, revenue, impressions/CTR and comments locally through the official YouTube APIs, and to assemble media-kit snapshots and render ready-to-use charts. Editing features such as video updates and comment moderation are opt-in and read-only by default.19MIT
- AlicenseBqualityCmaintenanceProvides comprehensive access to YouTube Data, Analytics, and Reporting APIs, enabling AI assistants to manage videos, analyze performance, handle comments, and extract transcripts.40MIT
TDQS
Scored across 79 tools
Most tools are clearly separated by resource and context: public video/channel reads, owned-creator operations, selected-channel moderation, analytics, uploads, and preflight/execute pairs. The main ambiguity comes from the large number of similar-sounding comment, video, and analytics tools, which could still cause misselection at scale.
The set overwhelmingly follows a youtube_ + snake_case action pattern, with clear preflight/execute prefixes. Minor deviations such as youtube_search, youtube_trending, youtube_my_account, and youtube_auth_status are still readable but slightly break the verb_noun convention.
Seventy-nine tools is far too many for practical selection and is inflated by many preflight/execute pairs. The YouTube creator/public/moderation domain is broad, but this surface is heavy and likely burdens an agent despite granular descriptions.
Coverage is very broad: public search/read, owned-creator analytics, upload lifecycle, metadata, thumbnails, captions, playlists, comments, moderation, subscriptions, and local Takeout analytics are represented. Minor gaps remain, such as owned-video deletion and some channel/branding or live-streaming workflows, but core lifecycles are covered.