YouTube Music MCP
Related Servers
Alternatives to YouTube Music MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing YouTube Music playlists via Claude. Add and remove songs, create playlists, and ask Claude to suggest music — all through conversation.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows AI models to control YouTube Music playback through Google Chrome by searching and playing songs using song and artist names.22MIT
- FlicenseAqualityDmaintenanceA lightweight MCP server that enables AI assistants like Cursor and Claude to control Spotify playback, playlists, and manage tokens via OAuth.152-
- FlicenseNot gradedqualityCmaintenanceA lightweight MCP server that enables AI assistants to control Spotify playback and manage playlists.-
- AlicenseAqualityCmaintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.1187 npmMIT
- FlicenseNot gradedqualityDmaintenanceA production-grade MCP server that connects YouTube Music to AI assistants, enabling music search, library management, playlist creation, and personalized recommendations through 15 tools, 3 resources, and 3 prompts.1-
TDQS
Scored across 2 tools
The two tools have overlapping purposes that could cause confusion. Both 'playTrack' and 'searchTrack' involve searching for tracks on YouTube Music, with 'playTrack' additionally opening the top result in a browser. An agent might misselect between them when the intent is ambiguous, such as wanting to search without playing or vice versa, as the descriptions don't clearly delineate distinct use cases.
The tool names follow a consistent pattern throughout. Both use camelCase with a verb-noun structure ('playTrack' and 'searchTrack'), making them predictable and readable. There are no deviations or mixed conventions, which aids in clarity and usability.
The tool count of 2 feels too thin for a YouTube Music server's apparent scope. With only search and play functionality, there are obvious gaps like managing playlists, controlling playback, or accessing user data. This limited set may hinder agents from performing common music-related tasks, indicating an incomplete surface for the domain.
The tool surface is severely incomplete for a YouTube Music domain. It only covers searching and playing tracks, missing essential operations such as pausing, skipping, volume control, playlist management, or user authentication. These gaps will likely cause agent failures when attempting broader music interactions, as the current tools don't support a full lifecycle or common workflows.