Enables Claude to connect and interact with Spotify for music playback and management.
Enables Claude to connect and interact with Spotify for music playback and management. Exposed over MCP by the spotify mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
MCP project to connect Claude with Spotify. Built on top of spotipy-dev's API.
Everything the assistant can do here goes through one of these:
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 sureDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPYou will need 6 environment variables: SPOTIFY_REDIRECT_URI, SPOTIFY_CLIENT_ID, YOUR_CLIENT_ID, SPOTIFY_CLIENT_SECRET, YOUR_CLIENT_SECRET, UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Spotify's toolset — Troubleshooting, Debugging — is a fair guide to whether it matches your workflow. It is maintained by boristopalov; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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 y |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
{
"mcpServers": {
"spotify-2": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"SPOTIFY_REDIRECT_URI": "your-value",
"SPOTIFY_CLIENT_ID": "your-value",
"YOUR_CLIENT_ID": "your-value",
"SPOTIFY_CLIENT_SECRET": "your-value",
"YOUR_CLIENT_SECRET": "your-value",
"UV_PUBLISH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SPOTIFY_REDIRECT_URI | Filesystem location the server is allowed to use. | Optional |
| SPOTIFY_CLIENT_ID | Configuration value read at startup. | Optional |
| YOUR_CLIENT_ID | Configuration value read at startup. | Optional |
| SPOTIFY_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| YOUR_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.