mcpField
S
Spotify MCP

Spotify MCP

Local
github.com/varunnealMedia & Design613Updated 33w ago

About Spotify MCP

Spotify MCP is an MCP server that connects Claude with Spotify, built on the spotipy-dev API. It is aimed at users who want to control playback and manage playlists through conversation. The project is marked as inactive, and most pull requests will not be merged.

Key features

  1. 01Start, pause and skip playback
  2. 02Search tracks, albums, artists and playlists
  3. 03Get details on tracks, albums, artists and playlists
  4. 04Manage the Spotify playback queue
  5. 05Create and update playlists

Use cases

  1. 01Controlling Spotify playback through an LLM chat
  2. 02Searching music by description and organizing playlists
  3. 03Looking up album or artist details

MCP support

The project runs as an MCP server that connects Claude to Spotify and exposes playback control, search and playlist management to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"spotify": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/inspector"
]
}
}
}
Run commandnpx -y @modelcontextprotocol/inspector

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@modelcontextprotocol/inspector

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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

Demo

Video -- turn on audio https://github.com/user-attachments/assets/20ee1f92-f3e3-4dfa-b945-ca57bc1e0894

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.