SpotifyMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | Yes | Your Spotify application client ID | |
| SPOTIFY_CLIENT_SECRET | Yes | Your Spotify application client secret | |
| SPOTIFY_REFRESH_TOKEN | Yes | Your Spotify refresh token for authentication |
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_songsC | Search for songs on Spotify |
| create_playlistB | Create a new Spotify playlist and return the URI to ALWAYS present to the user as a hyperlink |
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 2 tools
The two tools have clearly distinct purposes: one creates playlists, the other searches for songs. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (create_playlist, search_songs) with clear and predictable structure.
With only 2 tools, the surface is too thin for a comprehensive music service like Spotify. This falls in the borderline range for tool count.
The set lacks many essential operations such as playing music, managing playlists (get, update, delete), and user library actions, leaving significant gaps.