spotify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | Yes | Your Spotify client ID from the Spotify Developer Dashboard. | |
| SPOTIFY_REDIRECT_URI | Yes | The redirect URI set in the Spotify app (must be http://localhost:8888). | http://localhost:8888 |
| SPOTIFY_CLIENT_SECRET | Yes | Your Spotify client secret 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| SpotifyPlaybackA | Manage playback: get current track, start/resume, pause, skip, previous, seek, set volume. - get: info about the current track. - start: play spotify_uri, or resume if omitted. - pause / skip / previous. - seek: jump to position_ms. - volume: set volume_percent (0-100). |
| SpotifySearchC | Search for tracks, albums, artists, or playlists on Spotify. |
| SpotifyQueueB | Manage the playback queue - get the queue or add a track. |
| SpotifyGetInfoC | Get detailed info about a Spotify item (track, album, artist, or playlist). |
| SpotifyLibraryB | Manage saved (liked) tracks. - get_liked: list saved tracks. - save / remove: add or remove track_ids from the library. |
| SpotifyPlaylistA | Manage playlists. - list: the current user's playlists. - create: make a new playlist (name required). - add_tracks / remove_tracks: modify a playlist's items (playlist_id + track_ids required). - delete: remove a playlist from your library (playlist_id required). Spotify has no hard delete; this unfollows it, which removes owned playlists from your view. |
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 targets a distinct area of Spotify: info retrieval, library management, playback, playlists, queue, and search. No overlap in functionality.
All tool names follow a consistent PascalCase pattern with the prefix 'Spotify' and a noun indicating the function (e.g., SpotifyGetInfo, SpotifyPlayback).
With 6 tools, the server is well-scoped, covering the core Spotify operations without being too sparse or overloaded.
The tool set covers essential operations like search, get info, library, playlists, playback, and queue. Minor gaps such as editing playlist details or recommendations are missing, but core workflows are complete.