fetchtranscript-mcp
OfficialRelated Servers
Alternatives to fetchtranscript-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to fetch YouTube video transcripts with precise timestamps, multi-language support, and time-range filtering.31MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to fetch YouTube transcripts with timestamps, search within a video, and keep a local searchable memory of every transcript fetched.4MIT

fetchworks-mcpofficial
AlicenseAqualityDmaintenanceEnables AI agents to retrieve YouTube transcripts from individual videos, channels, and search results, supporting multiple output formats such as plain text, SRT, and VTT.337 npmMIT- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to extract and retrieve transcripts from YouTube videos in multiple languages, supporting various URL formats with zero local installation.MIT
- AlicenseAqualityBmaintenanceAllows AI agents to fetch, search, and summarize YouTube video transcripts without an API key, including chapter summaries.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and MCP clients to fetch YouTube video captions with timestamps, title, channel, and available languages, and to export transcripts as text, SRT, or WebVTT. It works with watch, Shorts, youtu.be, embed links, or bare video IDs without an API key.MIT
TDQS
Scored across 8 tools
Each tool targets a clearly distinct resource or action: transcript, comments, metadata, chapters, languages, channel info, channel video listing, and search. There is no meaningful overlap between any pair, and argument shapes reinforce the distinctions.
All tool names use a consistent snake_case verb_noun pattern (get_, list_, search_) with predictable resource suffixes. The use of get_ vs list_ vs search_ is semantically coherent and easy to follow.
Eight tools is well-scoped for a YouTube transcript and metadata server, with each tool earning its place. Nothing feels redundant or conspicuously absent from the count perspective.
The surface covers the core lifecycle well: transcript retrieval, language discovery, comments, metadata, chapters, channel info, channel videos, and search. Minor gaps exist—e.g., no comment-reply retrieval or in-transcript search—but agents can work around these for most transcript-focused workflows.