No user-submitted related servers found.
Scored across 53 tools
Most tools have clear resource+action pairs, but the audio-analysis group (compare, features, audit) and the two search tools (search, podcast_discover) have overlapping responsibilities that could cause misselection. The sampling tool for liked songs also blurs with the paginated saved_tracks tool.
All tools use a consistent lowercase snake_case verb_noun pattern with the spotify_ prefix (e.g., spotify_play, spotify_pause, spotify_playlist_create). Even the DJ and podcast subdomains follow the same convention, making naming predictable.
With 53 tools, the surface is extreme for an MCP server, even for a broad domain like Spotify. The count far exceeds the 25+ threshold and makes the set overwhelming, risking agent confusion and excessive selection overhead.
The server covers most major Spotify workflows: library management, playback control, playlists, podcast/saved episodes, and audio analysis. However, there is no direct tool for fetching a single track or artist details, leaving minor gaps in basic metadata retrieval.