Spotify MCP Node Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| playMusicB | Start playing a Spotify track, album, artist, or playlist |
| playbackActionC | Perform a playback action (pause, resume, skip to next, skip to previous) |
| searchSpotifyB | Search Spotify by keyword and field filters (e.g. artist, track, playlist, tag:new, tag:hipster) and return items of the given type |
| getNowPlayingA | Get information about the currently playing track on Spotify |
| getUserPlaylistsC | Get a list of the current user's playlists on Spotify |
| getPlaylistTracksC | Get a list of tracks in a Spotify playlist |
| getRecentlyPlayedB | Get a list of recently played tracks on Spotify |
| getFollowedArtistsB | Get a list of artists the user is following on Spotify |
| getUserTopItemsC | Get a list of the user's top artists or tracks |
| addToQueueA | Adds a track, album, artist or playlist to the playback queue |
| addTracksToPlaylistC | Add tracks to a Spotify playlist |
| createPlaylistB | Create a new playlist on Spotify |
| removeTracksFromPlaylistC | Remove tracks from a Spotify playlist |
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 13 tools
Most tools have distinct purposes, but 'addToQueue' and 'playMusic' could cause confusion as both involve initiating playback. 'addToQueue' adds to the queue while 'playMusic' starts playback immediately, but an agent might misinterpret their overlap in handling tracks/albums/artists/playlists. Other tools are clearly differentiated by resource and action.
All tool names follow a consistent verb_noun or verbNoun pattern, such as 'addToQueue', 'createPlaylist', 'getNowPlaying', and 'searchSpotify'. The naming is uniform across all 13 tools, with no mixing of conventions like camelCase and snake_case, making it predictable and readable.
With 13 tools, this server is well-scoped for Spotify integration, covering core functionalities like playback control, playlist management, user data retrieval, and search. Each tool serves a clear purpose without redundancy, fitting within the typical 3-15 tool range for such a domain.
The tool set provides comprehensive coverage for Spotify operations, including CRUD for playlists (create, add/remove tracks, get tracks), playback control (play, queue, actions), and user data (playlists, top items, followed artists, recently played). Minor gaps include no update/delete for playlists or explicit volume control, but agents can work around these with available tools.