A
licenseNot graded
qualityB
maintenanceFetches YouTube video subtitles (transcripts) over MCP, enabling clients like Claude to retrieve and summarize video content.
80 npm
MIT
Capslane YouTube transcript MCP server
OfficialRelated Servers
Alternatives to Capslane YouTube transcript MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible assistants to retrieve caption text from YouTube videos as either plain text or timestamped snippets for reading, summarizing, or searching. Supports local stdio and stateless HTTP deployments for integration with Claude Desktop, Claude Code, Cursor, and similar clients.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI client to obtain the text of a YouTube video by returning its metadata, the captions YouTube already provides, or a Whisper transcription run on a local GPU. Text responses are bounded and pageable, and long transcriptions run as background jobs that survive request timeouts.MIT
- FlicenseAqualityDmaintenanceProvides YouTube video transcripts (text and metadata) as MCP tools for AI hosts like Claude Code, enabling summarization, search, and Q&A without watching the video.2-
- AlicenseNot gradedqualityBmaintenanceFetches YouTube video transcripts with timestamps and provides them to LLM agents via MCP, enabling natural language access to video content.80 npm4MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to fetch YouTube video transcripts with precise timestamps, multi-language support, and time-range filtering.31MIT
TDQS
A4.4/5.0
Scored across 3 tools
Disambiguation4/5
The three tools have largely distinct purposes: fetching content, polling job status, and listing languages. However, get_youtube_transcript and list_available_languages both consume transcript units and populate the cache, creating mild ambiguity about when to use one versus the other.
Naming Consistency5/5
All three tools follow a clean verb_noun snake_case pattern (get_youtube_transcript, get_transcript_status, list_available_languages). Names are predictable and readable.
Tool Count4/5
Three tools for a narrowly scoped transcript-retrieval service is reasonable and each earns its place. It leans slightly thin, with no bulk or batch operation, but the domain doesn't demand more.
Completeness4/5
The surface covers the core lifecycle: retrieve transcript, poll async job status, and list available languages. Minor gaps exist (e.g., no explicit cancel/delete job operation, despite the status tool referencing cancelled jobs), but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues