Spotify

What is spotify-mcp?

spotify-mcp is a Model Context Protocol (MCP) server that enables Large Language Models (LLMs) to interact with Spotify. It acts as a bridge, translating natural language commands from an LLM into actions on Spotify, such as playing music, searching for tracks, and managing playlists.

How to use spotify-mcp?

To use spotify-mcp, you need to configure it with your Spotify API keys and integrate it with an MCP-enabled client like Claude Desktop or Cursor. You'll need to create an app on the Spotify developer dashboard to obtain your Client ID and Client Secret, and set a redirect URI. The project can be run either by adding a snippet to your MCP Config (using uvx for remote fetching or uv for local execution) or by cloning the repository and running it locally. Detailed instructions for configuring API keys and setting up the project within your MCP client are provided in the README.

Key Features of spotify-mcp

• Playback Control: Start, pause, and skip playback.
• Search Functionality: Search for tracks, albums, artists, and playlists.
• Information Retrieval: Get detailed information about tracks, albums, artists, and playlists.
• Queue Management: Manage the Spotify playback queue.
• Playlist Management: Manage, create, and update playlists.

Use Cases of spotify-mcp

• Voice-controlled Music: Control Spotify playback and search for music using natural language commands through an LLM.
• Automated Playlists: Create and manage Spotify playlists programmatically via an LLM.
• Music Information Retrieval: Quickly get details about songs, artists, or albums by asking an LLM.
• Integration with AI Assistants: Enhance AI assistants with Spotify capabilities, allowing them to fulfill music-related requests.

FAQ about spotify-mcp

• Q: What are the prerequisites for using spotify-mcp? A: You need Spotify API keys (Client ID, Client Secret, Redirect URI) and an MCP-enabled client (e.g., Claude Desktop). A Spotify Premium account is also required for using the developer API.
• Q: How do I get Spotify API keys? A: Create an account on developer.spotify.com, navigate to the dashboard, and create an app with http://127.0.0.1:8080/callback as the redirect URI.
• Q: Where can I find the Claude Desktop config file? A: On macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%/Claude/claude_desktop_config.json.
• Q: What should I do if I encounter issues? A: Ensure uv is updated (recommended >=0.54), verify Claude has execution permissions (chmod -R 755), and confirm you have Spotify Premium. You can also check logs (on Mac: ~/Library/Logs/Claude) or use the MCP Inspector for debugging.
• Q: Are there any limitations or deprecated features? A: Yes, some recommendation features have been deprecated by the Spotify API. Future updates will focus on minor features and project health, such as adding tests and support for paginated search results.

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 Claude 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.

"spotify": {
  "command": "uvx",
  "args": [
    "--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

Alternatively 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. Make sure claude has 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, and others for contributions.