Skip to main content
Glama
Spotify MCP Server

Spotify MCP Server

by makesh-kumar

A lightweight Model Context Protocol (MCP) server that enables AI assistants like Cursor & Claude to control Spotify playback and manage playlists.

Example Interactions

  • "Play Elvis's first song"

  • "Create a Taylor Swift / Slipknot fusion playlist"

  • "Copy all the techno tracks from my workout playlist to my work playlist"

Related MCP server: Spotify MCP Node Server

Tools

Read Operations

  1. searchSpotify

    • Description: Search for tracks, albums, artists, or playlists on Spotify

    • Parameters:

      • query (string): The search term

      • type (string): Type of item to search for (track, album, artist, playlist)

      • limit (number, optional): Maximum number of results to return (10-50)

    • Returns: List of matching items with their IDs, names, and additional details

    • Example: searchSpotify("bohemian rhapsody", "track", 20)

  2. getNowPlaying

    • Description: Get information about the currently playing track on Spotify

    • Parameters: None

    • Returns: Object containing track name, artist, album, playback progress, duration, and playback state

    • Example: getNowPlaying()

  3. getMyPlaylists

    • Description: Get a list of the current user's playlists on Spotify

    • Parameters:

      • limit (number, optional): Maximum number of playlists to return (default: 20)

      • offset (number, optional): Index of the first playlist to return (default: 0)

    • Returns: Array of playlists with their IDs, names, track counts, and public status

    • Example: getMyPlaylists(10, 0)

  4. getPlaylistTracks

    • Description: Get a list of tracks in a specific Spotify playlist

    • Parameters:

      • playlistId (string): The Spotify ID of the playlist

      • limit (number, optional): Maximum number of tracks to return (default: 100)

      • offset (number, optional): Index of the first track to return (default: 0)

    • Returns: Array of tracks with their IDs, names, artists, album, duration, and added date

    • Example: getPlaylistTracks("37i9dQZEVXcJZyENOWUFo7")

  5. getRecentlyPlayed

    • Description: Retrieves a list of recently played tracks from Spotify.

    • Parameters:

      • limit (number, optional): A number specifying the maximum number of tracks to return.

    • Returns: If tracks are found it returns a formatted list of recently played tracks else a message stating: "You don't have any recently played tracks on Spotify".

    • Example: getRecentlyPlayed({ limit: 10 })

  6. getUsersSavedTracks

    • Description: Get a list of tracks saved in the user's "Liked Songs" library

    • Parameters:

      • limit (number, optional): Maximum number of tracks to return (1-50, default: 50)

      • offset (number, optional): Offset for pagination (0-based index, default: 0)

    • Returns: Formatted list of saved tracks with track names, artists, duration, track IDs, and when they were added to Liked Songs. Shows pagination info (e.g., "1-20 of 150").

    • Example: getUsersSavedTracks({ limit: 20, offset: 0 })

Play / Create Operations

  1. playMusic

    • Description: Start playing a track, album, artist, or playlist on Spotify

    • Parameters:

      • uri (string, optional): Spotify URI of the item to play (overrides type and id)

      • type (string, optional): Type of item to play (track, album, artist, playlist)

      • id (string, optional): Spotify ID of the item to play

      • deviceId (string, optional): ID of the device to play on

    • Returns: Success status

    • Example: playMusic({ uri: "spotify:track:6rqhFgbbKwnb9MLmUQDhG6" })

    • Alternative: playMusic({ type: "track", id: "6rqhFgbbKwnb9MLmUQDhG6" })

  2. pausePlayback

    • Description: Pause the currently playing track on Spotify

    • Parameters:

      • deviceId (string, optional): ID of the device to pause

    • Returns: Success status

    • Example: pausePlayback()

  3. skipToNext

    • Description: Skip to the next track in the current playback queue

    • Parameters:

      • deviceId (string, optional): ID of the device

    • Returns: Success status

    • Example: skipToNext()

  4. skipToPrevious

    • Description: Skip to the previous track in the current playback queue

    • Parameters:

      • deviceId (string, optional): ID of the device

    • Returns: Success status

    • Example: skipToPrevious()

  5. createPlaylist

    • Description: Create a new playlist on Spotify

    • Parameters:

      • name (string): Name for the new playlist

      • description (string, optional): Description for the playlist

      • public (boolean, optional): Whether the playlist should be public (default: false)

    • Returns: Object with the new playlist's ID and URL

    • Example: createPlaylist({ name: "Workout Mix", description: "Songs to get pumped up", public: false })

  6. addTracksToPlaylist

    • Description: Add tracks to an existing Spotify playlist

    • Parameters:

      • playlistId (string): ID of the playlist

      • trackUris (array): Array of track URIs or IDs to add

      • position (number, optional): Position to insert tracks

    • Returns: Success status and snapshot ID

    • Example: addTracksToPlaylist({ playlistId: "3cEYpjA9oz9GiPac4AsH4n", trackUris: ["spotify:track:4iV5W9uYEdYUVa79Axb7Rh"] })

  7. addToQueue

    • Description: Adds a track, album, artist or playlist to the current playback queue

      • Parameters:

      • uri (string, optional): Spotify URI of the item to add to queue (overrides type and id)

      • type (string, optional): Type of item to queue (track, album, artist, playlist)

      • id (string, optional): Spotify ID of the item to queue

      • deviceId (string, optional): ID of the device to queue on

    • Returns: Success status

    • Example: addToQueue({ uri: "spotify:track:6rqhFgbbKwnb9MLmUQDhG6" })

    • Alternative: addToQueue({ type: "track", id: "6rqhFgbbKwnb9MLmUQDhG6" })

Album Operations

  1. getAlbums

    • Description: Get detailed information about one or more albums by their Spotify IDs

    • Parameters:

      • albumIds (string|array): A single album ID or array of album IDs (max 20)

    • Returns: Album details including name, artists, release date, type, total tracks, and ID. For single album returns detailed view, for multiple albums returns summary list.

    • Example: getAlbums("4aawyAB9vmqN3uQ7FjRGTy") or getAlbums(["4aawyAB9vmqN3uQ7FjRGTy", "1DFixLWuPkv3KT3TnV35m3"])

  2. getAlbumTracks

    • Description: Get tracks from a specific album with pagination support

    • Parameters:

      • albumId (string): The Spotify ID of the album

      • limit (number, optional): Maximum number of tracks to return (1-50)

      • offset (number, optional): Offset for pagination (0-based index)

    • Returns: List of tracks from the album with track names, artists, duration, and IDs. Shows pagination info.

    • Example: getAlbumTracks("4aawyAB9vmqN3uQ7FjRGTy", 10, 0)

  3. saveOrRemoveAlbumForUser

    • Description: Save or remove albums from the user's "Your Music" library

    • Parameters:

      • albumIds (array): Array of Spotify album IDs (max 20)

      • action (string): Action to perform: "save" or "remove"

    • Returns: Success status with confirmation message

    • Example: saveOrRemoveAlbumForUser(["4aawyAB9vmqN3uQ7FjRGTy"], "save")

  4. checkUsersSavedAlbums

    • Description: Check if albums are saved in the user's "Your Music" library

    • Parameters:

      • albumIds (array): Array of Spotify album IDs to check (max 20)

    • Returns: Status of each album (saved or not saved)

    • Example: checkUsersSavedAlbums(["4aawyAB9vmqN3uQ7FjRGTy", "1DFixLWuPkv3KT3TnV35m3"])

Setup

Prerequisites

  • Node.js v16+

  • A Spotify Premium account

  • A registered Spotify Developer application

Installation

git clone https://github.com/marcelmarais/spotify-mcp-server.git
cd spotify-mcp-server
npm install
npm run build

Creating a Spotify Developer Application

  1. Go to the Spotify Developer Dashboard

  2. Log in with your Spotify account

  3. Click the "Create an App" button

  4. Fill in the app name and description

  5. Accept the Terms of Service and click "Create"

  6. In your new app's dashboard, you'll see your Client ID

  7. Click "Show Client Secret" to reveal your Client Secret

  8. Click "Edit Settings" and add a Redirect URI (e.g., http://127.0.0.1:8888/callback)

  9. Save your changes

Spotify API Configuration

Create a spotify-config.json file in the project root (you can copy and modify the provided example):

# Copy the example config file
cp spotify-config.example.json spotify-config.json

Then edit the file with your credentials:

{
  "clientId": "your-client-id",
  "clientSecret": "your-client-secret",
  "redirectUri": "http://127.0.0.1:8888/callback"
}

Authentication Process

The Spotify API uses OAuth 2.0 for authentication. Follow these steps to authenticate your application:

  1. Run the authentication script:

npm run auth
  1. The script will generate an authorization URL. Open this URL in your web browser.

  2. You'll be prompted to log in to Spotify and authorize your application.

  3. After authorization, Spotify will redirect you to your specified redirect URI with a code parameter in the URL.

  4. The authentication script will automatically exchange this code for access and refresh tokens.

  5. These tokens will be saved to your spotify-config.json file, which will now look something like:

{
  "clientId": "your-client-id",
  "clientSecret": "your-client-secret",
  "redirectUri": "http://localhost:8888/callback",
  "accessToken": "BQAi9Pn...kKQ",
  "refreshToken": "AQDQcj...7w",
  "expiresAt": 1677889354671
}
  1. The server will automatically refresh the access token when needed, using the refresh token.

Integrating with Claude Desktop, Cursor, and VsCode Via Cline model extension

To use your MCP server with Claude Desktop, add it to your Claude configuration:

{
  "mcpServers": {
    "spotify": {
      "command": "node",
      "args": ["spotify-mcp-server/build/index.js"]
    }
  }
}

For Cursor, go to the MCP tab in Cursor Settings (command + shift + J). Add a server with this command:

node path/to/spotify-mcp-server/build/index.js

To set up your MCP correctly with Cline ensure you have the following file configuration set cline_mcp_settings.json:

{
  "mcpServers": {
    "spotify": {
      "command": "node",
      "args": ["~/../spotify-mcp-server/build/index.js"],
      "autoApprove": ["getListeningHistory", "getNowPlaying"]
    }
  }
}

You can add additional tools to the auto approval array to run the tools without intervention.

Available Tools

19 tools
addToQueueA

Adds a track, album, artist or playlist to the playback queue

Inputs: uri, type, id, deviceId.

addTracksToPlaylistC

Add tracks to a Spotify playlist

Inputs: playlistId (required), trackIds (required), position.

checkUsersSavedAlbumsC

Check if albums are saved in the user's "Your Music" library

Inputs: albumIds (required).

createPlaylistB

Create a new playlist on Spotify

Inputs: name (required), description, public.

getAlbumsC

Get detailed information about one or more albums by their Spotify IDs

Inputs: albumIds (required).

getAlbumTracksC

Get tracks from a specific album with pagination support

Inputs: albumId (required), limit, offset.

getMyPlaylistsB

Get a list of the current user's playlists on Spotify

Inputs: limit.

getNowPlayingA

Get information about the currently playing track on Spotify

Inputs: no named parameters.

getPlaylistTracksB

Get a list of tracks in a Spotify playlist

Inputs: playlistId (required), limit, offset.

getQueueC

Get a list of the currently playing track and the next items in your Spotify queue

Inputs: limit.

getRecentlyPlayedB

Get a list of recently played tracks on Spotify

Inputs: limit.

getUsersSavedTracksA

Get a list of tracks saved in the user's "Liked Songs" library

Inputs: limit, offset.

pausePlaybackA

Pause Spotify playback on the active device

Inputs: deviceId.

playMusicB

Start playing a Spotify track, album, artist, or playlist

Inputs: uri, type, id, deviceId.

resumePlaybackB

Resume Spotify playback on the active device

Inputs: deviceId.

saveOrRemoveAlbumForUserC

Save or remove albums from the user's "Your Music" library

Inputs: albumIds (required), action (required).

searchSpotifyB

Search for tracks, albums, artists, or playlists on Spotify

Inputs: query (required), type (required), limit.

skipToNextA

Skip to the next track in the current Spotify playback queue

Inputs: deviceId.

skipToPreviousA

Skip to the previous track in the current Spotify playback queue

Inputs: deviceId.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as getNowPlaying for current track info and getQueue for queue details, but some overlap exists: addToQueue and playMusic both handle playback initiation, which could cause confusion. However, descriptions clarify that addToQueue adds to queue without playing, while playMusic starts playback, mitigating ambiguity.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with clear actions like get, add, create, and skip, using camelCase throughout. Minor deviations include saveOrRemoveAlbumForUser, which is more verbose, and checkUsersSavedAlbums, which uses 'check' instead of 'get', but overall the naming is predictable and readable.

    Tool Count4/5

    With 19 tools, the count is slightly high but reasonable for a comprehensive Spotify integration covering playback, library management, playlists, and search. It includes essential operations without being overly bloated, though it borders on feeling heavy compared to simpler servers.

    Completeness5/5

    The tool set provides complete coverage for Spotify's core domain: playback control (play, pause, skip, queue), library management (save/remove albums, get saved tracks), playlist operations (create, add tracks, get tracks), and search. No obvious gaps exist; agents can perform full workflows from discovery to playback and organization.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Spotify playback, search for music, manage playlists, and access library information through the Spotify API. Requires Spotify Premium for playback control features.
      4
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to control Spotify playback, search the full catalog including podcasts and audiobooks, manage libraries and playlists, and understand listening taste.
      131
      116 npm
      1
      MIT