ytptube-mcp
Related Servers
Alternatives to ytptube-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage multiple named YouTube accounts through one local stdio server, covering video upload and scheduling, metadata, captions, playlists, comments, live broadcasts and chat, channel branding, and analytics reporting via the official Google APIs. It also offers optional FFmpeg-based local media tools for probing, muxing audio, normalizing loudness, trimming, burning subtitles, and extracting thumbnails.MIT
- AlicenseNot gradedqualityCmaintenanceA 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.3MIT
- AlicenseNot gradedqualityAmaintenanceA fully functional MCP server and CLI for YouTube to automate YouTube operation.712Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables users to control a MeTube instance for managing yt-dlp video and audio downloads through AI assistants. It supports operations like queuing URLs, listing active downloads, and managing authentication cookies.92MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for authenticated YouTube writes, enabling video uploads, caption tracks, playlist management, and metadata edits with safety guards and async jobs.2MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for fetching YouTube video transcripts and metadata using yt-dlp. It provides tools for transcript retrieval, subtitle listing, video info, and cookie management to bypass YouTube rate limits.-
TDQS
Scored across 28 tools
Every tool has a distinct purpose: reading vs writing, history vs tasks vs presets vs system state. Even the patch/update pairs are clearly differentiated by partial vs full replacement.
All tools use the 'ytptube_' prefix followed by a verb_noun pattern (e.g., list_tasks, create_preset, validate_cli_options). Minor deviations like 'live_queue' are still readable and do not break the overall consistency.
With 28 tools, the server exceeds the 25-tool threshold for 'too many'. While each tool covers a distinct API operation, the sheer number makes the surface area heavy and harder to navigate.
Core download lifecycle and task/preset management are covered, but obvious gaps exist: there is no delete operation for tasks or presets, and system configuration and yt-dlp options are read-only with no set/update functionality.