Spotify MCP

What is Spotify MCP?

Spotify MCP is a Model Context Protocol server that connects Claude with Spotify, built on top of the Spotipy library. It enables controlling Spotify playback, searching the music library, and managing playlists through natural language commands in an MCP-enabled client like Claude Desktop.

How to use Spotify MCP?

Configure with Spotify API credentials (client ID, client secret, and a redirect URI like http://127.0.0.1:8080/callback) and add the server to your MCP config. Run with uvx (e.g., uvx --python 3.12 --from git+https://github.com/varunneal/spotify-mcp spotify-mcp) or run locally after cloning the repo. A Spotify Premium account is required for the developer API.

Key features of Spotify MCP

• Start, pause, and skip playback
• Search for tracks, albums, artists, and playlists
• Get info about a track, album, artist, or playlist
• Manage the Spotify queue
• Manage, create, and update playlists

Use cases of Spotify MCP

• Control Spotify playback hands-free via Claude conversations
• Find and play music by describing what you want to hear
• Build and modify playlists using natural language
• Queue up songs for a listening session without opening Spotify

FAQ from Spotify MCP

What are the prerequisites?

A Spotify Premium account, a Spotify Developer app with a redirect URI (must use http and a loopback address), and uv version 0.54 or newer.

How do I find logs for troubleshooting?

On macOS, Claude Desktop logs are in ~/Library/Logs/Claude. On other platforms, refer to the MCP quickstart guide for log locations.

How can I avoid being asked to authorize every tool call?

Run the project locally by cloning the repository and using uv --directory /path/to/spotify-mcp run spotify-mcp in your MCP config instead of uvx.

Is this project actively maintained?

As of March 2026 the project is marked as inactive, and most pull requests will not be merged.

What authentication method does it use?

It uses Spotify OAuth via client ID, client secret, and a redirect URI. The redirect URI must be set to an explicit loopback address (e.g., http://127.0.0.1:8080/callback).