Skip to main content
Glama
thenavidm

YouTube MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to YouTube MCP

No user-submitted related servers found.

    Related Servers

    • mcp-server-youtube

      vaporif
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search videos, read channels, browse playlists, fetch comments, and get transcripts from YouTube using the YouTube Data API v3 and InnerTube API for captions.
      2
      GPL 3.0

    • YouTube MCP Server

      rai-wasif
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search videos, retrieve transcripts and metadata, analyze channels, and access trending and engagement analytics for YouTube content.
      21 npm
      -

    • vunm-youtube-mcp

      vunm-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with YouTube channels, providing analytics, video metadata updates, transcript extraction, and comment management through official Google APIs with OAuth 2.0.
      MIT

    • youtube-mcp

      gimslab
      A
      license
      A
      quality
      D
      maintenance
      Enables AI tools to access YouTube content, including transcript extraction, video/channel info, and search.
      4
      12 npm
      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.1/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: transcripts (get_transcript/search_transcript/get_transcripts), videos (get_video/list_my_videos/search_videos), and channels (get_channel/get_my_channel/get_channel_analytics). The main confusion points are get_transcript vs get_transcripts (singular reads one, plural batches 20) and get_channel vs get_my_channel vs get_channel_analytics, but descriptions clarify each.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_, list_, search_, analyze_, update_, reply_to_, delete_). The only variation is intentional qualifiers like `my`/`transcripts`, which remain predictable and readable.

    Tool Count4/5

    16 tools is slightly above the ideal range but each earns its place across the read/write/analytics surface. The set covers transcripts, video details, search, comments, channel stats, and mutations without obvious redundancy.

    Completeness4/5

    Strong coverage of reading (video, channel, transcript, comments, search, analytics) and video lifecycle (update_video, delete_video), plus comment replies. The notable gap is video creation/upload and top-level comment posting, which agents cannot work around for those workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources