yt-mcp
Related Servers
Alternatives to yt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables searching YouTube Music and managing playlists through read and confirmation-gated write tools over STDIO. Supports identity checks, song search, playlist listing/retrieval, and previewed playlist creation, track addition, and exact track removal.MIT
- AlicenseNot gradedqualityCmaintenanceProvides a local stdio MCP server for controlling YouTube Music through the CLI, enabling playback, search, queue management, and library access via MCP-compatible clients.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for YouTube Music that enables searching songs and artists, managing playlists, and authenticating via Google OAuth, using STDIO transport.-
- FlicenseNot gradedqualityCmaintenanceEnables searching YouTube Music and managing playlists: create/delete playlists, add/remove/reorder tracks, and more via natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search for music and create/manage playlists on YouTube Music via OAuth 2.0 authentication.1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to search YouTube Music, manage playlists, and retrieve listening history using the ytmusicapi library.6MIT
TDQS
Scored across 6 tools
Each tool targets a distinct action: searching, generating a single-seed radio, creating a playlist from that radio, generating a multi-seed radio, creating a playlist from a multi-seed radio, and resuming an existing playlist. Though some tools pair as get/create for the same seed type, the names and intended step in the workflow are clear.
All tools follow a consistent snake_case verb_noun pattern: search_songs, get_song_radio, create_private_radio_playlist, get_multi_seed_radio, create_private_multi_seed_radio_playlist, resume_private_playlist. The prefix clearly distinguishes action and the noun hierarchy is logical.
Six tools are well-scoped for a YouTube Music radio playlist server. There are enough tools to cover the basic discovery and playlist creation flow without overwhelming the agent, and each tool contributes a meaningful operation.
The surface covers search, radio creation (single and multi-seed), playlist creation from both, and resuming a saved track plan, which supports the core workflow end-to-end. Minor gaps exist—such as no explicit update or delete playlist operations—but they are outside the apparent main purpose and can be worked around by re-creating.