Skip to main content
Glama
Sign In
CreatorOS

CreatorOS

by matteys001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CreatorOS

No user-submitted related servers found.

    Related Servers

    • youtube-analytics-mcp

      adilsonicjunior
      A
      license
      Not graded
      quality
      C
      maintenance
      A local, read-only MCP server that provides Claude with private YouTube Analytics data—views, retention, traffic sources, demographics, revenue, and impressions/CTR—via authenticated Google APIs.
      7 npm
      MIT

    • youtube-studio-mcp

      ujorgeleite
      F
      license
      A
      quality
      B
      maintenance
      A local MCP server that exposes your own YouTube channel's data—such as channel metrics, video listings, retention curves, and pillar performance—to Claude Code via stdio.
      5
      -

    • youtube-creator-mcp

      t4god
      A
      license
      Not graded
      quality
      C
      maintenance
      A local, privacy-first MCP server providing direct access to official YouTube Data, Analytics, Reporting, and Live Streaming APIs for creators, enabling channel analysis, research, and guarded management operations.
      3
      MIT

    • YouTube Ultimate Toolkit MCP

      Comzee
      A
      license
      A
      quality
      C
      maintenance
      A comprehensive MCP server that provides Claude AI with full access to YouTube content, including searchable transcripts, metadata, comments, and playlists. It uniquely supports capturing video screenshots and extracting audio clips for analysis across both local and remote platforms.
      5
      32 npm
      3
      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

    A3.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools split cleanly into four groups: connection management, library browsing, analytics, and recommendations. Most boundaries are clear, but the analytics cluster has mild overlap risk — get_channel_analytics vs analyze_channel_performance (the latter is a composite that calls the former) and get_video_analytics vs compare_videos require reading descriptions to pick correctly. list_videos vs search_videos could also be confused at a glance, though the quota note helps.

    Naming Consistency5/5

    Every tool follows the same youtube_<verb>_<noun> snake_case pattern, with predictable verb families (connect, list, set, get, search, analyze, recommend, compare). No camelCase or style drift anywhere in the set.

    Tool Count5/5

    15 tools is at the top of the ideal band and each one maps to a distinct user-facing job — connection lifecycle, video browsing, channel/video analytics, and recommendations. Nothing feels padded, and the composite analyze_channel_performance earns its place by tying the others together.

    Completeness4/5

    The surface covers the full connection lifecycle plus the read-only insight workflows the server explicitly scopes itself to (OAuth read-only), so core jobs have no dead ends. Minor gaps remain: no playlist or subscription inspection, no video metadata update, and no way to drill into comment replies, all of which an agent might reasonably expect from a creator-analytics server.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources