Spotify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | Yes | Your Spotify Client ID obtained from the Spotify Developer Dashboard. | |
| SPOTIFY_CLIENT_SECRET | Yes | Your Spotify Client Secret obtained from the Spotify Developer Dashboard. | |
| SPOTIFY_REFRESH_TOKEN | Yes | Your Spotify Refresh Token obtained by running the authorization script. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_musicB | Search for songs, artists, albums, or playlists on Spotify |
| get_current_trackB | Get the currently playing track |
| play_trackC | Play a specific track by its URI or ID |
| pause_playbackB | Pause the current playback |
| resume_playbackB | Resume the current playback |
| skip_to_nextB | Skip to the next track |
| skip_to_previousB | Skip to the previous track |
| like_trackA | Add the current or specified track to your Liked Songs |
| unlike_trackA | Remove the current or specified track from your Liked Songs |
| create_playlistC | Create a new playlist |
| add_to_playlistC | Add tracks to a playlist |
| get_top_tracksC | Get your top tracks |
| get_top_artistsB | Get your top artists |
| set_volumeC | Set playback volume |
| toggle_shuffleC | Turn shuffle on or off |
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 15 tools
Each tool has a clearly distinct purpose targeting specific Spotify actions like playback control, playlist management, or user data retrieval. No tools overlap in functionality, making it easy for an agent to select the right one without confusion.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'add_to_playlist', 'get_current_track', and 'toggle_shuffle'. This uniformity enhances readability and predictability across the toolset.
With 15 tools, the server is well-scoped for managing Spotify's core features like playback, search, playlists, and user preferences. Each tool serves a clear purpose, and the count aligns with the domain's complexity without being excessive or insufficient.
The toolset covers essential Spotify operations including playback control, search, playlist management, and user interactions like liking tracks. Minor gaps exist, such as missing album-specific actions or detailed playlist editing, but core workflows are well-supported.