searchSpotifyLABSCO SUMMARY
Discovery and the playlist in the same conversation.
The read tools carry it: search the obscure end of a genre, look at what is already in your workout playlists, and build something from both without switching apps. Premium is not optional here — the project ties it to Spotify's developer terms, so a free account will not do.
What it is
A Node server over the Spotify API for playback control and playlist work, aimed at discovery — asking for the lesser-known end of a genre and then building a playlist out of what comes back.
What you get
- searchSpotify for tracks, artists and albums
- getNowPlaying for what is playing right now
- getUserPlaylists for your own playlists, getPlaylistTracks for what is inside one
- Playback and playlist-creation operations alongside the read tools
- Works from Claude Desktop, Cursor and Windsurf
Requirements
A Spotify Premium account — the project states Spotify's Developer Terms require it — and a Spotify developer application for the API credentials, authorised once. The project also asks that you opt out of data sharing for model training if you use this with an AI assistant.
Setup effort
Build from source — git clone https://github.com/igorgarbuz/spotify-mcp.git
USE CASES
01
Finding music you would not have found by browsing
Ask for lesser-known tracks in a genre or similar to an artist, and search each suggestion to confirm it exists before adding it.
02
Building a playlist out of ones you already have
Read your playlists, pull the tracks from the ones you want to draw on, and assemble the new list from those.
03
Identifying what is playing and doing something with it
Read the current track, then search for the artist's other work in the same breath.
04
Checking what is actually in a playlist before you change it
List its tracks first, so an addition does not duplicate something already there.
14 tools
Listed in project docs. Your client may show a different list.
getNowPlayinggetUserPlaylistsgetPlaylistTracksgetRecentlyPlayedgetFollowedArtistsgetUserTopItemsplayMusicpausePlaybackskipToNextskipToPreviouscreatePlaylistaddTracksToPlaylistaddToQueueBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation. The documentation numbers 15 tools, but getRecentlyPlayed is listed twice, so there are 14 distinct tools. getListeningHistory, seen only in the autoApprove example, is not a tool.
Requires
node on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/igorgarbuz/spotify-mcp.git
cd spotify-mcp
npm install
npm run build
cp spotify-config.example.json spotify-config.jsonEdit spotify-config.json: add your Spotify app's Client ID as clientId, and set redirectUri to the redirect URI you registered in the Spotify Developer Dashboard (http://127.0.0.1:8888/callback is the simplest).
TERMINAL
npm run authMCP Clients
Claude Desktop, Windsurf
Add the following to the configuration; <YOUR_PATH_TO_SPOTIFY_MCP> is the absolute path of the folder you cloned and built above:
JSON
{
"mcpServers": {
"spotify": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SPOTIFY_MCP>/build/index.js"
]
}
}
}Cline
Add the following to the configuration; <YOUR_PATH_TO_SPOTIFY_MCP> is the absolute path of the folder you cloned and built above:
CLINE · JSON
{
"mcpServers": {
"spotify": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SPOTIFY_MCP>/build/index.js"
],
"autoApprove": [
"getNowPlaying"
]
}
}
}cline_mcp_settings.json
