Skip to main content
Glama
Spotify MCP Server

Spotify MCP Server

by varunneal

spotify-mcp MCP server

MCP project to connect Claude with Spotify. Built on top of spotipy-dev's API.

[Notice March 2026]: Inactive project. Most PRs will not be merged.

Features

  • Start, pause, and skip playback

  • Search for tracks/albums/artists/playlists

  • Get info about a track/album/artist/playlist

  • Manage the Spotify queue

  • Manage, create, and update playlists

Related MCP server: Vulpes Spotify MCP Server

Demo

Configuration

Getting Spotify API Keys

Create an account on developer.spotify.com. Navigate to the dashboard. Create an app with redirect_uri as http://127.0.0.1:8080/callback. You can choose any port you want but you must use http and an explicit loopback address (IPv4 or IPv6).

See here for more info/troubleshooting. You may have to restart your MCP environment (e.g. Claude Desktop) once or twice before it works.

Locating MCP Config

For Cursor, Claude Desktop, or any other MCP-enabled client you will have to locate your config.

  • Claude Desktop location on MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json

  • Claude Desktop location on Windows: %APPDATA%/Claude/claude_desktop_config.json

Run this project with uvx

Add this snippet to your MCP Config.

{
  "mcpServers": {
    "spotify": {
      "command": "uvx",
      "args": [
        "--python", "3.12",
        "--from", "git+https://github.com/varunneal/spotify-mcp",
        "spotify-mcp"
      ],
      "env": {
        "SPOTIFY_CLIENT_ID": YOUR_CLIENT_ID,
        "SPOTIFY_CLIENT_SECRET": YOUR_CLIENT_SECRET,
        "SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8080/callback"
      }
    }
  }
}

Run this project locally

Using UVX will open the spotify redirect URI for every tool call. To avoid this, you can run this project locally by cloning this repo:

git clone https://github.com/varunneal/spotify-mcp.git

Add it to your MCP Config like this:

"spotify": {
    "command": "uv",
    "args": [
      "--directory",
      "/path/to/spotify-mcp",
      "run",
      "spotify-mcp"
    ],
    "env": {
      "SPOTIFY_CLIENT_ID": YOUR_CLIENT_ID,
      "SPOTIFY_CLIENT_SECRET": YOUR_CLIENT_SECRET,
      "SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8080/callback"
    }
  }

Troubleshooting

Please open an issue if you can't get this MCP working. Here are some tips:

  1. Make sure uv is updated. I recommend version >=0.54.

  2. If cloning locally, enable execution permisisons for the project: chmod -R 755.

  3. Ensure you have Spotify premium (needed for running developer API).

This MCP will emit logs to std err (as specified in the MCP) spec. On Mac the Claude Desktop app should emit these logs to ~/Library/Logs/Claude. On other platforms you can find logs here.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /path/to/spotify-mcp run spotify-mcp

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

TODO

Unfortunately, a bunch of cool features have now been deprecated from the Spotify API. Most new features will be relatively minor or for the health of the project:

  • tests.

  • adding API support for managing playlists.

  • adding API support for paginated search results/playlists/albums.

PRs appreciated! Thanks to @jamiew, @davidpadbury, @manncodes, @hyuma7, @aanurraj, @JJGO and others for contributions.

Available Tools

5 tools
SpotifyGetInfoA

Get detailed information about a Spotify item (track, album, artist, or playlist).

Inputs: item_uri (required).

SpotifyPlaybackB

Manages the current playback with the following actions: - get: Get information about user's current track. - start: Starts playing new item or resumes current playback if called with no uri. - pause: Pauses current playback. - skip: Skips current track.

Inputs: action (required), spotify_uri, num_skips.

SpotifyPlaylistC

Manage Spotify playlists. - get: Get a list of user's playlists. - get_tracks: Get tracks in a specific playlist. - add_tracks: Add tracks to a specific playlist. - remove_tracks: Remove tracks from a specific playlist. - change_details: Change details of a specific playlist. - create: Create a new playlist.

Inputs: action (required), playlist_id, track_ids, name, +2 more.

SpotifyQueueB

Manage the playback queue - get the queue or add tracks.

Inputs: action (required), track_id.

SpotifySearchB

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

Inputs: query (required), qtype, limit.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: GetInfo for metadata, Playback for player control, Playlist for playlist management, Queue for queue operations, and Search for finding content. However, there is some potential overlap between GetInfo and Search, as both can retrieve item details, though GetInfo is more specific to known items while Search is for discovery.

    Naming Consistency4/5

    Tool names follow a consistent 'Spotify' prefix and descriptive noun-based naming (e.g., SpotifyPlayback, SpotifyPlaylist). The internal actions within tools (like get, start, pause) are also consistent. A minor deviation is that some tools use underscores in action names (e.g., get_tracks), while others do not, but overall the pattern is clear and readable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for Spotify integration, covering key areas like playback control, playlist management, search, and queue handling. Each tool serves a distinct purpose without being overly broad or too narrow, making it manageable and functional for typical agent tasks.

    Completeness4/5

    The tool set covers core Spotify functionalities: playback control, playlist CRUD operations, search, and queue management. Minor gaps include lack of user profile management (e.g., get user info) or more advanced features like recommendations, but the essential workflows for playing music and managing content are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers