SpotifyMCP
Related Servers
Alternatives to SpotifyMCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Spotify playback, search music, manage playlists and library, and access user listening insights via the Spotify Web API.-
- FlicenseBqualityDmaintenanceEnables AI assistants to control Spotify playback, search for music, manage playlists, and interact with your Spotify library through natural language commands.19-
- FlicenseBqualityBmaintenanceEnables AI assistants to control Spotify playback, search the catalog, and manage playlists and liked songs through natural language. Supports reading currently playing tracks, queues and devices, plus play, pause, skip, queueing, volume control, and playlist creation and editing.30-
- FlicenseAqualityDmaintenanceEnables AI assistants to control Spotify playback, search for music, manage playlists, and access library information through the Spotify API. Requires Spotify Premium for playback control features.4-
- AlicenseBqualityDmaintenanceEnables AI assistants to control Spotify playback, manage playlists, search music, and access listening history. Requires Spotify Premium and uses secure OAuth 2.0 with PKCE authentication.1353 npmMIT
- AlicenseBqualityBmaintenanceConnects AI assistants to the Spotify Web API, enabling playback control, search, and recommendations.8MIT
TDQS
Scored across 608 tools
With 608 tools, the surface is saturated with near-duplicates: get_now_playing vs get_currently_playing vs get_playback_snapshot, listening_streaks vs listening_streak_report, playlist_intersect vs playlist_intersection, b_sides_finder vs b_sides_detector, plus roughly 20 URI-parsing utilities and 30+ snapshot tools. Explicit legacy aliases help at the margins, but an agent cannot reliably disambiguate such overlapping clusters.
Names mix verb_noun (get_track, create_playlist), noun_verb (playlist_sort, playlist_intersect), bare verbs (play, pause, mute, seek), and there is no consistent preview/commit pattern (sort_playlist_plan vs playlist_sort vs sort_playlist_apply; reverse_playlist_plan vs playlist_reverse). Arbitrary aliasing like get_show_episodes/list_show_episodes and statsfm_taste_profile/taste_profile adds further chaos.
608 tools is an extreme count for any MCP server, far beyond the 50+ threshold for a failing score. The scope could be served by a small fraction of these tools; dozens of report tools, snapshot variants, and URI helpers are redundant.
The server covers the full Spotify API surface plus stats.fm and local sidecar features: playback, library, playlists, search, podcasts, audiobooks, analytics, snapshots, and mutation tracking. Missing features are mostly removed API endpoints (artist top tracks, user profile) with explicit disclosures, and genuine gaps (queue clear, insert-next) have documented workarounds.