Spotify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| searchSpotifyB | Search for tracks, albums, artists, or playlists on Spotify |
| getNowPlayingA | Get information about the currently playing track on Spotify |
| getMyPlaylistsB | Get a list of the current user's playlists on Spotify |
| getPlaylistTracksB | Get a list of tracks in a Spotify playlist |
| getRecentlyPlayedB | Get a list of recently played tracks on Spotify |
| getUsersSavedTracksA | Get a list of tracks saved in the user's "Liked Songs" library |
| getQueueC | Get a list of the currently playing track and the next items in your Spotify queue |
| playMusicB | Start playing a Spotify track, album, artist, or playlist |
| pausePlaybackA | Pause Spotify playback on the active device |
| skipToNextA | Skip to the next track in the current Spotify playback queue |
| skipToPreviousA | Skip to the previous track in the current Spotify playback queue |
| createPlaylistB | Create a new playlist on Spotify |
| addTracksToPlaylistC | Add tracks to a Spotify playlist |
| resumePlaybackB | Resume Spotify playback on the active device |
| addToQueueA | Adds a track, album, artist or playlist to the playback queue |
| getAlbumsC | Get detailed information about one or more albums by their Spotify IDs |
| getAlbumTracksC | Get tracks from a specific album with pagination support |
| saveOrRemoveAlbumForUserC | Save or remove albums from the user's "Your Music" library |
| checkUsersSavedAlbumsC | Check if albums are saved in the user's "Your Music" library |
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 19 tools
Most tools have distinct purposes, such as getNowPlaying for current track info and getQueue for queue details, but some overlap exists: addToQueue and playMusic both handle playback initiation, which could cause confusion. However, descriptions clarify that addToQueue adds to queue without playing, while playMusic starts playback, mitigating ambiguity.
Tool names follow a consistent verb_noun pattern with clear actions like get, add, create, and skip, using camelCase throughout. Minor deviations include saveOrRemoveAlbumForUser, which is more verbose, and checkUsersSavedAlbums, which uses 'check' instead of 'get', but overall the naming is predictable and readable.
With 19 tools, the count is slightly high but reasonable for a comprehensive Spotify integration covering playback, library management, playlists, and search. It includes essential operations without being overly bloated, though it borders on feeling heavy compared to simpler servers.
The tool set provides complete coverage for Spotify's core domain: playback control (play, pause, skip, queue), library management (save/remove albums, get saved tracks), playlist operations (create, add tracks, get tracks), and search. No obvious gaps exist; agents can perform full workflows from discovery to playback and organization.