Spotify API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | No | Your Spotify app's client ID | |
| SPOTIFY_CLIENT_SECRET | No | Your Spotify app's client secret |
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 |
|---|---|
| spotify_searchC | Search for tracks, artists, albums, or playlists on Spotify |
| spotify_authenticateC | Authenticate with Spotify using OAuth 2.0 |
| spotify_get_user_profileB | Get the current user's profile information |
| spotify_create_playlistC | Create a new playlist for the authenticated user |
| spotify_add_tracks_to_playlistC | Add tracks to a playlist |
| spotify_get_user_playlistsC | Get the current user's playlists |
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 6 tools
Each tool has a clearly distinct purpose: authentication, user profile retrieval, playlist creation, playlist listing, track addition to playlists, and general search. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'spotify_verb_noun' pattern with snake_case, such as spotify_authenticate and spotify_add_tracks_to_playlist. This predictability enhances usability and reduces confusion.
With 6 tools, the server is well-scoped for basic Spotify API interactions, covering authentication, user data, playlist management, and search. Each tool serves a clear purpose without being excessive or insufficient.
The toolset covers core Spotify workflows like authentication, user profile access, playlist creation/listing, and search, but lacks update or delete operations for playlists or tracks, which are minor gaps that agents can work around.