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.
      17 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
      9 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 a distinct resource+action (search_videos vs get_video vs analyze_channel vs get_channel_analytics), and the transcript family is well separated by purpose. The main risk is get_channel vs get_my_channel and get_transcript vs get_transcripts, but the descriptions explicitly explain when to use which, so an agent can disambiguate reliably.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_channel, list_accounts, search_videos, update_video, delete_video, reply_to_comment). The `my`/`transcripts` variants are still within the same convention, so there is no stylistic drift.

    Tool Count4/5

    16 tools is on the heavier side but each one maps to a clear capability (read, search, analytics, moderation, mutation), so nothing feels redundant. It sits just above the ideal band but remains well-scoped for the breadth of the YouTube domain.

    Completeness4/5

    Coverage is strong: channel/video read, search, transcripts, comments, analytics, plus update and delete for videos and comment replies. The notable gap is video creation/upload and playlist management, which means the lifecycle is read/update/delete without a create path, but core analysis and management workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources