MCP Claude Spotify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | Yes | The Client ID obtained from the Spotify Developer Dashboard. | |
| SPOTIFY_CLIENT_SECRET | Yes | The Client Secret obtained from the Spotify Developer Dashboard. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth-spotifyC | Authenticate with Spotify |
| search-spotifyC | Search for tracks, albums, artists, or playlists on Spotify |
| get-current-playbackB | Get information about the user's current playback state |
| play-trackC | Play a specific track on an active device |
| pause-playbackB | Pause the user's playback |
| next-trackB | Skip to the next track |
| previous-trackB | Skip to the previous track |
| get-user-playlistsB | Get a list of the user's playlists |
| create-playlistC | Create a new playlist for the current user |
| add-tracks-to-playlistC | Add tracks to a playlist |
| get-recommendationsC | Get track recommendations based on seeds |
| get-top-tracksB | Get the user's top played tracks over a specified time range |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose targeting specific Spotify operations like playback control, playlist management, search, and user data retrieval. There is no overlap or ambiguity between tools like 'pause-playback' and 'next-track' or 'get-user-playlists' and 'create-playlist'.
Most tools follow a consistent verb_noun pattern (e.g., 'create-playlist', 'get-recommendations', 'pause-playback'), but there are minor deviations like 'auth-spotify' (noun_verb) and 'search-spotify' (verb_noun with appended service name). The naming is still highly readable and predictable.
With 12 tools, this server is well-scoped for Spotify integration, covering essential areas like authentication, playback control, playlist management, search, and recommendations. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for core Spotify workflows, including CRUD-like operations for playlists, playback control, and data retrieval. Minor gaps exist, such as no explicit 'update-playlist' or 'delete-playlist' tools, but agents can work around these using available tools like 'add-tracks-to-playlist' and playlist management functions.