spotify-mcp
by varunneal
spotify-mcp is an MCP server that connects Claude with Spotify, built on top of the spotipy-dev's API. It allows users to control Spotify playback and manage their music library through Claude.
Last updated: N/A
What is spotify-mcp?
spotify-mcp is a Model Context Protocol (MCP) server designed to integrate Spotify with the Claude AI assistant. It leverages the Spotipy API to enable Claude to interact with Spotify's functionalities.
How to use spotify-mcp?
To use spotify-mcp, you need to obtain Spotify API keys by creating an app on the Spotify Developer Dashboard and configuring the redirect URI. Then, clone the repository, add the tool as an MCP server in Claude's configuration file (claude_desktop_config.json), and set the environment variables for the Spotify API keys.
Key features of spotify-mcp
Start, pause, and skip playback
Search for tracks/albums/artists/playlists
Get info about a track/album/artist/playlist
Manage the Spotify queue
Use cases of spotify-mcp
Controlling Spotify playback via voice commands through Claude
Searching for music and adding it to the queue using Claude
Getting information about currently playing tracks or artists through Claude
Managing Spotify playlists using Claude
FAQ from spotify-mcp
What do I need to run this MCP?
What do I need to run this MCP?
You need a Spotify Premium account, Spotify API keys, and Claude installed.
What if I can't get this MCP working?
What if I can't get this MCP working?
Make sure uv is updated to version >=0.54, Claude has execution permissions for the project (chmod -R 755), and you have Spotify premium. Check the logs in ~/Library/Logs/Claude (Mac) or the location specified in the documentation.
What redirect URI should I use?
What redirect URI should I use?
Use http://localhost:8888 or any other port on localhost with HTTP.
How do I debug the MCP?
How do I debug the MCP?
Use the MCP Inspector via npx @modelcontextprotocol/inspector uv --directory /path/to/spotify_mcp run spotify-mcp.
What features are planned for the future?
What features are planned for the future?
Future features include tests, adding API support for managing playlists, and adding API support for paginated search results/playlists/albums.