mcp-youtube
Related Servers
Alternatives to mcp-youtube
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables managing a YouTube channel from Claude by listing, searching, editing, and organizing videos and playlists while retrieving channel, video, and thumbnail insights.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to list videos in any public YouTube playlist and fetch their transcripts, so users can summarize, search, and ask questions across playlist content.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
- FlicenseNot gradedqualityDmaintenanceEnables Claude to search YouTube for artists and manage playlists on your YouTube account.1-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with YouTube Data API for searching videos, channels, and playlists, and retrieving details and playlists.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to inspect your YouTube playlists for recently added videos and retrieve new items since the last check, powering daily automation that schedules videos into calendar slots.1MIT
TDQS
Scored across 52 tools
Most tools target a distinct resource+action clearly (e.g., list-playlists vs. get-playlist vs. create-playlist). A few pairs like list-videos and list-activities, or list-comments and list-comment-threads, could cause initial confusion but their descriptions differentiate them well. Overall, boundaries are clear despite the large surface.
All tool names follow a consistent lowercase kebab-case verb-noun pattern (e.g., list-channels, create-comment-thread, upload-caption). Even multi-word actions like set-comment-moderation-status adhere to the same scheme. The pattern is predictable and aids discoverability.
52 tools is heavy, exceeding the typical 'too many' threshold. However, the server aims to cover the entire YouTube Data API surface, and most tools map to distinct endpoints or logical operations. Some tools (e.g., list-i18n-languages, list-membership-levels) feel peripheral, but overall the size is defensible.
CRUD/Lifecycle coverage is strong for videos, playlists, comments, captions, and channel sections. Notable gaps include a dedicated get-channel tool for fetching arbitrary channel metadata (only list-channels for own channel), and no way to fetch a playlist's metadata without owning it via list-playlists. Some resources like subscriptions and memberships lack full lifecycle support but list/action tools cover core needs.