A
licenseA
qualityC
maintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.
11
87 npm
MIT
Spotify MCP Server
by llyfn
Related Servers
Alternatives to Spotify MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA FastMCP server that exposes Spotify's catalog and user context as tools for Claude, enabling track search, audio features, artist discography, recommendations, currently playing, and playlist creation.-
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude Desktop to interact with Spotify's music streaming service, supporting playback control, playlist management, music search, and user profile access.412-
- FlicenseAqualityDmaintenanceA lightweight MCP server that enables AI assistants like Cursor and Claude to control Spotify playback, playlists, and manage tokens via OAuth.152-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Spotify, allowing them to search for tracks, control playback, and manage playlists.1-
- AlicenseAqualityDmaintenanceMCP server for Spotify that lets AI agents search music, control playback, and manage playlists via the Spotify Web API.1924 npmMIT
TDQS
B3.4/5.0
Scored across 59 tools
Disambiguation5/5
Each tool targets a distinct resource and action (e.g., get_album vs. get_albums vs. get_album_tracks). Even with many similar resources, the verb-noun pattern clearly differentiates operations, and no two tools have overlapping purposes.
Naming Consistency4/5
Most tools follow a consistent verb_noun snake_case pattern (e.g., get_album, create_playlist, set_volume). However, 'whoami' deviates from this pattern, and there are mixed prefixes like 'check_' and 'unfollow_' alongside 'follow_', causing minor inconsistency.
Tool Count2/5
With 59 tools, the set is overly large for an MCP server. While the Spotify API is broad, this many tools can overwhelm users and agents, and the calibration suggests 25+ is too many. Several tools could potentially be merged (e.g., multiple get_saved_* tools).
Completeness3/5
The tool set covers essential operations (CRUD for playlists, playback control, library management, following, and search). However, notable gaps exist, such as the absence of a delete_playlist tool, missing audio features/analysis, and lack of recommendations.
Maintenance
ActivityInactive
ResponsivenessNo issues