MCP Spotify Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | Yes | Your Spotify API Client ID obtained from the Spotify Developer Dashboard | |
| SPOTIFY_CLIENT_SECRET | Yes | Your Spotify API 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 |
|---|---|
| get_access_tokenB | Get a valid Spotify access token for API requests |
| searchC | Search for tracks, albums, artists, or playlists |
| get_artistC | Get Spotify catalog information for an artist |
| get_multiple_artistsC | Get Spotify catalog information for multiple artists |
| get_artist_top_tracksB | Get Spotify catalog information about an artist's top tracks |
| get_artist_related_artistsB | Get Spotify catalog information about artists similar to a given artist |
| get_artist_albumsC | Get Spotify catalog information about an artist's albums |
| get_albumC | Get Spotify catalog information for an album |
| get_album_tracksB | Get Spotify catalog information for an album's tracks |
| get_multiple_albumsC | Get Spotify catalog information for multiple albums |
| get_trackC | Get Spotify catalog information for a track |
| get_available_genresB | Get a list of available genres for recommendations |
| get_new_releasesC | Get a list of new album releases featured in Spotify |
| get_recommendationsB | Get track recommendations based on seed tracks, artists, or genres |
| get_audiobookC | Get Spotify catalog information for an audiobook |
| get_multiple_audiobooksC | Get Spotify catalog information for multiple audiobooks |
| get_audiobook_chaptersB | Get Spotify catalog information about an audiobook's chapters |
| get_playlistC | Get a playlist owned by a Spotify user |
| get_playlist_tracksC | Get full details of the tracks of a playlist |
| get_playlist_itemsC | Get full details of the items of a playlist |
| modify_playlistC | Change a playlist's name and public/private state |
| add_tracks_to_playlistC | Add one or more tracks to a playlist |
| remove_tracks_from_playlistC | Remove one or more tracks from a playlist |
| get_current_user_playlistsC | Get a list of the playlists owned or followed by the current Spotify user |
| get_featured_playlistsC | Get a list of Spotify featured playlists |
| get_category_playlistsC | Get a list of Spotify playlists tagged with a particular category |
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 26 tools
Most tools have distinct purposes targeting specific resources (e.g., albums, artists, playlists), but there is some overlap between get_playlist_items and get_playlist_tracks, which could cause confusion as both retrieve playlist content. The descriptions clarify that get_playlist_tracks focuses on tracks specifically, while get_playlist_items is more general, but the distinction is subtle and might lead to misselection.
Tool names follow a highly consistent verb_noun pattern throughout, with all tools using snake_case and starting with verbs like 'get', 'add', 'remove', or 'modify'. This predictability makes it easy for agents to understand and navigate the toolset without confusion.
With 26 tools, the count feels excessive for a Spotify API server, as many tools could be consolidated (e.g., multiple 'get' tools for similar resources). This bloat may overwhelm agents and complicate decision-making, indicating a lack of streamlined design for the domain.
The toolset provides comprehensive coverage of the Spotify domain, including CRUD operations for playlists (add, remove, modify), extensive catalog access for albums, artists, tracks, and audiobooks, and features like search, recommendations, and user-specific data. No obvious gaps exist, ensuring agents can handle a wide range of Spotify-related tasks.