Spotify MCP

What is Spotify MCP about?

Spotify MCP enables Large Language Models to interact with the Spotify service, providing commands for playback control, catalog search, and playlist manipulation.

How to use Spotify MCP?

1. Obtain Spotify API credentials (client ID, client secret, and set a redirect URI).
2. Add an MCP server entry to your Claude Desktop / Cursor configuration, either using uvx for on‑the‑fly execution or cloning the repository and running it with uv.
3. Set the required environment variables (SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REDIRECT_URI).
4. Invoke the MCP from your LLM‑enabled client to perform actions like start, pause, skip, search tracks, or edit playlists.

Key features of Spotify MCP

• Start, pause, and skip playback
• Search tracks, albums, artists, and playlists
• Retrieve detailed information about media items
• Manage the playback queue
• Create, update, and delete playlists

Use cases of Spotify MCP

• Voice‑like assistants that can control music while you work
• Automated playlist generation based on user preferences
• Context‑aware music recommendations within chat workflows
• Integration of music actions into broader productivity automations

FAQ from the Spotify MCP

Do I need a Spotify Premium account? Yes, the developer API actions used by this MCP require a Premium subscription.

What Python version is required? The uvx configuration runs with Python 3.12.

Can I run the server locally without opening the redirect URI each call? Yes, clone the repository and execute it with uv as described in the README.

Which operating systems are supported? The MCP works on macOS, Windows, and Linux as long as the required environment variables and Python runtime are available.

How are logs accessed? Logs are written to STDERR. On macOS they appear in ~/Library/Logs/Claude; other platforms follow the standard MCP log locations.

spotify-mcp MCP server

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

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

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.