A
licenseA
qualityB
maintenanceMCP server for the Spotify Web API — gives Claude and other AI assistants tools to search music, control playback, manage playlists, library, and podcasts.
47
MIT
Spotify MCP Server
by varunneal
Related Servers
Alternatives to Spotify MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- 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-
- 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-
- FlicenseNot gradedqualityDmaintenanceConnects Claude with Spotify to control playback, search music, get track information, and manage the queue through conversation.1-
TDQS
B3.3/5.0
Scored across 5 tools
Disambiguation4/5
Most tools have distinct purposes: GetInfo for metadata, Playback for player control, Playlist for playlist management, Queue for queue operations, and Search for finding content. However, there is some potential overlap between GetInfo and Search, as both can retrieve item details, though GetInfo is more specific to known items while Search is for discovery.
Naming Consistency4/5
Tool names follow a consistent 'Spotify' prefix and descriptive noun-based naming (e.g., SpotifyPlayback, SpotifyPlaylist). The internal actions within tools (like get, start, pause) are also consistent. A minor deviation is that some tools use underscores in action names (e.g., get_tracks), while others do not, but overall the pattern is clear and readable.
Tool Count5/5
With 5 tools, the server is well-scoped for Spotify integration, covering key areas like playback control, playlist management, search, and queue handling. Each tool serves a distinct purpose without being overly broad or too narrow, making it manageable and functional for typical agent tasks.
Completeness4/5
The tool set covers core Spotify functionalities: playback control, playlist CRUD operations, search, and queue management. Minor gaps include lack of user profile management (e.g., get user info) or more advanced features like recommendations, but the essential workflows for playing music and managing content are well-supported.
Maintenance
ActivityInactive
ResponsivenessUnresponsive