Spotify MCP Server
Related Servers
Alternatives to Spotify MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceConnects Claude with Spotify, allowing users to control playback, search for music, get track/artist information, and manage the queue via the Spotify API.51-
- FlicenseAqualityDmaintenanceConnects Claude with Spotify, enabling playback control, search functionality, and queue management through Spotify's API.4-
- FlicenseNot gradedqualityDmaintenanceConnects Claude with Spotify to control playback, search music, get track information, and manage the queue through conversation.1-
- AlicenseNot gradedqualityDmaintenanceConnects Claude to Spotify, enabling play control, playlist management, lyrics retrieval, and music recommendations through natural language.1MIT
- AlicenseAqualityCmaintenanceEnables Claude to control Spotify playback, search tracks/albums/artists/playlists, and manage the queue via the Spotify API.6MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to control Spotify features including playback control, playlist management, search, and accessing user's listening history and preferences through the Spotify API.1-
TDQS
Scored across 28 tools
Most tools have clearly distinct purposes, and the descriptions carefully separate near-neighbors like get_saved_tracks vs check_saved_tracks. A few pairs (get_tracks/get_saved_tracks, unfollow_playlist/remove_tracks_from_playlist) are close enough in name to require reading descriptions carefully.
Tool names generally follow a clear verb_noun pattern, and sets like check_saved_* and remove_*_from_playlist are internally consistent. There is some inconsistency between get_ and list_ for collections (get_saved_tracks vs list_playlists vs list_devices), but it does not seriously impede readability.
28 tools is on the heavy side for a single MCP server, and the agent must juggle a large surface. Each tool does earn its place, but the count exceeds the range where the tool set feels tightly scoped.
The set covers playlists, saved tracks, search, and playback well, but album and artist library handling is one-sided: check_saved_albums and check_following_artists have no corresponding save/remove album or follow/unfollow artist tools. There is also no way to list saved albums, leaving obvious lifecycle gaps that will cause agent failures for those workflows.