Skip to main content
Glama
Webba-Creative-Technologies

Capslane YouTube transcript MCP server

Official
by Webba-Creative-Technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Capslane YouTube transcript MCP server

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

    • mcp-youtube-transcribe

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

    • YouTube Transcript MCP

      utjjalx-afk
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients and agents to fetch YouTube transcripts and caption lists from video IDs or links, preferring manual/auto captions by ordered language preference and falling back to local Faster-Whisper audio transcription when captions are unavailable. Results include source, language, full text and timestamped segments, with CLI exports to JSON, text, SRT and WebVTT, all without paid APIs or API keys.
      3
      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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources