Skip to main content
Glama
YouTube Studio MCP

YouTube Studio MCP

by nelsonrogers

Related Servers

Alternatives to YouTube Studio MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access YouTube organic analytics, including channel stats, video performance, watch time, and audience engagement, via the YouTube Data API v3 and Analytics API v2.
      6
      30 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with comprehensive YouTube analytics and channel management capabilities, including channel performance, video analytics, audience insights, and content strategy tools.
      30 npm
      1
      -
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to query the full YouTube Analytics, Data v3, and Reporting API surface for one or multiple channels you own, with unrestricted parameters, local OAuth handling, and large-result output to files.
      13
      25 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Gives LLM agents read-only access to YouTube and Instagram analytics, returning engagement rates, performance versus a channel's median, outlier detection, and Shorts/Reels versus long-form splits for channels, videos, comments, posts, and hashtags. It also provides a prompt that audits a channel and proposes data-backed video ideas, with quota-aware caching and actionable error messages.
      8
      MIT

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have sharply distinct targets: auth status vs. authenticate, list_videos vs. get_videos_details vs. get_top_videos, and each analytics tool covers a different report (summary, time series, audience, traffic, retention, revenue). The overlap risk is concentrated in get_media_kit_data (a composite of nearly everything else) and query_analytics (escape hatch that can reproduce other tools' output), plus get_impressions vs. enable_impressions_reports, though the descriptions do state when to use each.

    Naming Consistency4/5

    Nearly all tools follow snake_case verb_noun (get_channel, list_videos, get_audience_breakdown, get_traffic_sources). Minor deviations exist: bare 'authenticate', the different verb style in 'query_analytics', and the awkward plural in 'get_videos_details' versus the singular 'get_channel'/'get_video' pattern. The enable_/get_ pair for impressions is a sensible sub-convention.

    Tool Count4/5

    At 19 tools the surface leans heavy for a single-platform server, but each tool maps to a real YouTube Studio/analytics view rather than duplicating another. Composite tools (get_media_kit_data, query_analytics) arguably consolidate several others, yet they serve distinct aggregation/escape-hatch use cases.

    Completeness4/5

    Analytics and reporting coverage is excellent: performance, trends, top content, audience, traffic, retention, revenue, impressions/CTR and a raw-query fallback, plus chart rendering. Gaps are on the write side — comments can be read but not replied to or moderated, and there is no video/playlist metadata editing or upload, though those are arguably outside a 'Studio reporting' scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues