Skip to main content
Glama
pauliusdotpro

YouTube Audio & Transcript MCP Server

by pauliusdotpro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to YouTube Audio & Transcript MCP Server

No user-submitted related servers found.

    Related Servers

    • fetchworks-mcp by Fetchworks

      fetchworks-mcpofficial

      Fetchworks
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to retrieve YouTube transcripts from individual videos, channels, and search results, supporting multiple output formats such as plain text, SRT, and VTT.
      3
      7 npm
      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

    • rippr

      mrslbt
      A
      license
      A
      quality
      C
      maintenance
      Extract YouTube transcripts for AI agents, RAG pipelines, and LLM workflows. Supports any YouTube URL. Returns clean text or timestamped segments. No API keys required.
      1
      4
      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

    Disambiguation5/5

    Each tool targets a clearly distinct action: youtube_to_audio produces audio files, youtube_transcript retrieves captions, and get_job polls async jobs from either. There is no realistic overlap that would cause misselection.

    Naming Consistency3/5

    The three names use three different patterns: youtube_to_audio (noun_to_noun with verb), youtube_transcript (noun_noun, no verb), and get_job (verb_noun). All are snake_case and readable, but the convention is mixed rather than predictable.

    Tool Count4/5

    Three tools is lean but each earns its place: two capabilities plus the shared async-job poller. It is slightly minimal (no batch/playlist helper), but well-scoped for the server's narrow purpose.

    Completeness4/5

    The core surface (audio extraction, transcript retrieval, and job-status handling for both async flows) is fully covered with no dead ends. Minor gaps exist: no playlist/batch support and no lightweight video metadata lookup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources