mcp-youtube-channel-transcript-extractor
Related Servers
Alternatives to mcp-youtube-channel-transcript-extractor
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceResolves TikTok handles or company domains to brand accounts, returning follower, like, video counts, verification status, and more.1227 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
- FlicenseAqualityDmaintenanceEnables AI assistants to analyze YouTube channels, videos, transcripts, and content strategy through structured tool calls.1711 npm-
- AlicenseAqualityAmaintenanceEnables resolving a company domain to its Instagram, Threads, and Facebook accounts with follower and post counts.1386 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables YouTube data crawling and AI-powered summarization of videos, including channel metadata retrieval, time-range queries, and automatic transcription with multi-language support.-
- AlicenseAqualityCmaintenanceChecks username availability and retrieves account information across major social media platforms including YouTube, TikTok, Threads, X (Twitter), and Instagram, perfect for brand name qualification and competitive research.1862 npmMIT
TDQS
Scored across 1 tool
With only one tool there is nothing to confuse it with, and the description clearly enumerates what it does (domain/handle → channel stats) and what it does not do (search, video listing, video detail). The only mild internal blur is that the tool name advertises transcripts while the body frames them as a gated option, but that is a scoping note, not a tool-selection ambiguity.
The single tool follows a clean snake_case verb_noun pattern (get_youtube_channel_stats). No mixing of conventions or vague verb styles is present to break predictability.
One tool is thin for a server that also implies transcript extraction and channel resolution; resolving, stats, and transcript pulling are collapsed into a single overloaded call. It is not mis-scoped enough to be wrong, but it sits at the borderline of too few.
Channel lookup and stats are covered, but the headline transcript capability is effectively unusable (caption content gated, reported as not_extractable), and there is no video listing, video detail, or multi-channel/batch operation. An agent can still retrieve channel stats, so gaps are notable rather than fatal.