XavierFabregat/spotify-mcp

Control Spotify by talking to your AI. An MCP server for Claude Desktop, Claude Code,
Cursor, and any other MCP client.
> **You:** play something like early Bill Evans
> **AI:** ▶ Now playing: *"Peace Piece" — Bill Evans · Everybody Digs Bill Evans*
>
> **You:** perfect, queue the whole album and save this one
> **AI:** ➕ Queued *Everybody Digs Bill Evans* · ❤️ Saved "Peace Piece" to your library
Built against the **current (post-February-2026) Spotify Web API** — many older
Spotify MCP servers predate those changes and are partially broken.
Requirements
- **Spotify Premium** — Spotify requires it for playback control and (since Feb 2026)
for creating the developer app you'll use.
- **Node.js ≥ 20**
Quick start
The wizard walks you through creating your own (free) Spotify developer app, asks for
its Client ID, and opens a browser to connect your account — about 2 minutes total.
Why your own app? Spotify caps third-party apps at a handful of users, so every user
brings their own; the wizard makes that painless. No client secret is involved (PKCE).
Tokens stay in ~/.spotify-mcp/ on your machine and refresh silently.
The one detail that must be exact — your app's Redirect URI:
Add to your MCP client
**Claude Code**
**Claude Desktop** (~/Library/Application Support/Claude/claude_desktop_config.json)
or **Cursor** (~/.cursor/mcp.json):
Restart the client and start talking.
Tools
| Tool | What it does |
|---|---|
| play | Play by free-text query (search → best match → play) or Spotify URI |
| playback | pause / resume / next / previous / seek / volume / shuffle / repeat |
| now_playing | Current track, progress, device, mode |
| queue | Add a track to the queue; show up next |
| devices | List devices; transfer playback |
| search | Browse tracks/albums/artists/playlists (max 10 per type — API cap) |
| get_playlists | List your playlists |
| get_playlist_items | Show a playlist's tracks (own/collaborative only — API restriction) |
| modify_playlist | Create a playlist; add tracks |
| library | Save / remove / check items in your library |
| authenticate | Run the Spotify login from inside a conversation |
Design
- **Tools are intents, not endpoints.** "Play some Radiohead" is one tool call —
the server searches, picks the best match, starts playback, and reports what it
chose so you can correct it. No search → choose → play round trips.
- **Small surface.** 11 tools instead of one per API endpoint keeps tool selection
accurate across different AI clients and context lean.
- **Responses are compact text with Spotify URIs**, so follow-ups ("queue that")
chain without re-searching. Raw API payloads never reach the model.
- **Errors are instructions.** No active device? The response lists your devices and
says how to pick one. Not logged in? It points at the authenticate tool. The