Skip to main content
Glama
youtube-transcript-leads-mcp

youtube-transcript-leads-mcp

by willowswt

Related Servers

Alternatives to youtube-transcript-leads-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to fetch transcripts for individual YouTube or TikTok videos, whole channels, and playlists, search YouTube, and track new uploads. It supports bulk extraction jobs, reusable transcript libraries, and read-only video listing with OAuth or API-key access.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pull captions from any public video in plain text, timestamped segments or SRT along with metadata, search YouTube with filters, and return creator or transcript-derived chapters. Also builds structured extractive summaries with keywords, notable quotes and timestamped deep links, without needing a YouTube API key or server-side LLM.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to pull full transcripts from YouTube videos, search videos and channels, browse a channel's complete upload history, search within a single channel, and extract every video in a playlist through one hosted remote endpoint. It supports API-key or OAuth 2.1 sign-in with no local installation, returning metadata and paginated results with stable error codes.
      10
      MIT
    • F
      license
      B
      quality
      Not graded
      maintenance
      Enables extraction and processing of YouTube video transcripts from individual videos, channels, and playlists. Supports transcript search, batch processing, multiple output formats (JSON, text, SRT, VTT), and bulk operations across multiple videos.
      11
      34 npm
      -

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly different resources and actions: one extracts transcripts/RAG chunks, the other discovers channel contact emails. There is no meaningful overlap that would cause an agent to misselect between them.

    Naming Consistency5/5

    Both names use consistent snake_case with a verb-first pattern and a shared YouTube domain prefix. The structure verb_youtube_resource_outcome is predictable across the set.

    Tool Count4/5

    Two tools are slightly below the typical 3-15 range, but each consolidates a broad, distinct workflow rather than being arbitrary. The count is reasonable for a narrowly focused transcript-and-leads server.

    Completeness4/5

    The surface covers the core workflows: transcript extraction with metadata/RAG chunks and channel discovery with email/social extraction. Minor gaps exist around batch operations or export/history features, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues