Skip to main content
Glama
KalpeshMahida0212

runsheet-mcp

by KalpeshMahida0212
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to runsheet-mcp

No user-submitted related servers found.

    Related Servers

    • youtube-mcp-server

      tuitamogamer-gpt
      A
      license
      A
      quality
      D
      maintenance
      A local stdio MCP server that gives Claude (or any MCP client) full programmatic control over a single YouTube channel, including video upload, channel management, comments, analytics, and more.
      46
      11 npm
      MIT

    • youtube-mcp

      GhOsT0407
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to control a YouTube channel through MCP, including uploading and editing videos, scheduling releases, and reading channel and video analytics via official APIs.
      8
      MIT

    • youtube-mcp-server

      nyagera
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables users to access their own YouTube channel, videos, and analytics through MCP-compatible clients such as ChatGPT and Claude, exposing tools for channel stats, video listing, video analytics, and video search.
      11 npm
      -

    • Youtube Uploader MCP

      anwerj
      A
      license
      Not graded
      quality
      A
      maintenance
      - Upload videos to YouTube from MCP - Client(Claude/Cursor/VS Code) - OAuth2 authentication flow - Access token and refresh token management - Multi Channel Support
      59
      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 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: reads are separated by channel, schedule, library, and watchlist, while local listing, text utilities, thumbnail generation, and upload have non-overlapping purposes. The descriptions make the boundaries clear, so an agent should not confuse them.

    Naming Consistency5/5

    All tools use the same runsheet_ prefix and snake_case verb_noun convention (get_*, list_*, count_*, preserve_*, style_*, make_*, upload_*), with no deviations or mixed styles.

    Tool Count5/5

    Eleven tools is well within the typical 3-15 range for a focused YouTube channel management server. Each tool appears to earn its place by covering a distinct read, utility, or upload operation.

    Completeness2/5

    Several descriptions reference write tools that are not present in the surface (runsheet_schedule_video, runsheet_update_metadata, runsheet_file_to_playlist, runsheet_break_down_breakout), creating dead ends for scheduling existing videos, updating metadata, filing to playlists, and breakout analysis. Missing core write operations beyond upload means agents will fail on common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources