Skip to main content
Glama
utjjalx-afk

YouTube Transcript MCP

by utjjalx-afk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to YouTube Transcript MCP

No user-submitted related servers found.

    Related Servers

    • mcp-youtube-transcript

      cchamp-msft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • youtube-summarize

      zlatkoc
      A
      license
      A
      quality
      C
      maintenance
      MCP server that fetches YouTube video transcripts and optionally summarizes them. Supports multiple transcript formats (text, JSON, SRT, WebVTT), multi-language retrieval, and flexible YouTube URL parsing.
      6
      51 PyPI
      6
      MIT

    • Nass MCP

      Mosabomer2000
      A
      license
      A
      quality
      C
      maintenance
      Enables transcription of YouTube videos by using available captions or falling back to actual audio with local Whisper ASR and multiple free providers. It supports job status, transcript retrieval and search, audio excerpts, and export formats while keeping source links and timestamps.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: get_transcript fetches transcript content, list_captions enumerates available caption tracks, and get_status reports local capabilities. There is no overlap in purpose, and the descriptions clearly delimit when to use each.

    Naming Consistency5/5

    All three tools follow a strict verb_noun convention (get_transcript, list_captions, get_status). The pattern is predictable and immediately readable.

    Tool Count4/5

    Three tools is a tight, well-scoped set for a narrow transcript-retrieval domain, with each tool earning its place. It is on the lean side, but nothing feels missing or redundant.

    Completeness4/5

    The surface covers the core lifecycle: discover captions, fetch transcript, and check capabilities/limits. Minor gaps like batch fetching or in-transcript search are outside the stated purpose and easily worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources