YouTube MCP Server
Related Servers
Alternatives to YouTube MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search videos, channels, and playlists, retrieve video metadata, transcripts, and comments via the YouTube Data API v3.46 PyPI68MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with YouTube through the YouTube Data API, allowing users to search for videos, playlists, and channels, generate video titles using AI, and manage YouTube content through natural language commands.22ISC
- AlicenseAqualityBmaintenanceEnables AI agents to search and rank YouTube videos by relevance and engagement, preview and adjust a candidate list, and create or manage playlists in the user's account with quota tracking and approval-gated writes.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search videos, read channels, browse playlists, fetch comments, and get transcripts from YouTube using the YouTube Data API v3 and InnerTube API for captions.2GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI models to search, retrieve, and analyze YouTube videos, channels, playlists, and transcripts via the YouTube Data API, with automatic API key failover.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to list, create, and modify playlists and their items, and to search for videos on a user's YouTube account through the YouTube Data API v3. Uses OAuth 2.0 with PKCE, quota-aware tools, and cached search results to keep daily API usage low.6MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: playPlaylist is for playing videos in the browser, while searchVideos is for searching and returning video metadata. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
The naming is inconsistent: playPlaylist uses camelCase, while searchVideos uses a verb_noun pattern. This mix of conventions lacks a predictable pattern, which could confuse agents expecting uniformity across tools.
With only 2 tools, the server feels thin for a YouTube domain, which typically involves operations like listing playlists, managing subscriptions, or uploading videos. The current set is insufficient for comprehensive YouTube interactions, suggesting a significant under-scoping.
The tool surface is severely incomplete for a YouTube server. It lacks basic CRUD operations such as creating playlists, managing subscriptions, or handling user accounts. The existing tools cover only playback and search, leaving major gaps that will likely cause agent failures in broader tasks.