youtube-transcript-mcp
Related Servers
Alternatives to youtube-transcript-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to extract and retrieve transcripts from YouTube videos in multiple languages, supporting various URL formats with zero local installation.72 npmMIT
- FlicenseAqualityCmaintenanceEnables fetching YouTube video transcripts with metadata, including timed captions in multiple formats (JSON, SRT, VTT, CSV, TXT) and preprocessing options.41-
- FlicenseNot gradedqualityCmaintenanceEnables retrieving plain-text transcripts from YouTube videos in any available language, including auto-generated captions, by providing a URL or video ID.-
- AlicenseAqualityDmaintenanceRetrieves transcripts from YouTube videos with support for multiple languages, timestamp control, and language detection. Enables video content analysis, summarization, and quote extraction without manually downloading or watching videos.2110 npm15MIT
- AlicenseNot gradedqualityDmaintenanceEnables retrieval of transcripts from YouTube videos, supporting multiple URL formats, language selection, timestamps, and ad filtering.1,072 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI models to extract transcripts from YouTube videos in multiple languages with zero local setup. It supports all YouTube URL formats and features smart caching via Cloudflare Workers for fast responses.72 npm1MIT
TDQS
Scored across 4 tools
Each tool targets a distinct concern: parsing URLs, fetching transcripts, listing caption languages, and summarizing video info. Although list_languages and video_info both mention captions, their purposes are clearly separated (exploring vs. explaining/planning).
All tool names follow the consistent pattern youtube_<verb>_<object>: parse_url, get_transcript, list_languages, video_info. The style is uniform and predictable across the set.
Four tools is a well-scoped size for a focused YouTube transcript server. Each tool serves a clear function without redundancy or bloat, covering the primary workflow.
The surface covers the core transcript workflow completely: parse/validate references, fetch transcripts, list available languages, and get video-level metadata to explain missing captions. There are no dead ends for the stated purpose.