Spotify MCP Server

Enables control of Spotify playback and management of your queue through a Model Context Protocol (MCP) server. The spotify mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

MCP project to connect Claude with Spotify. Built on top of spotipy-dev's API.

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

Adding it to your client

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.

Its toolset

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 sure
• Debugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP

Configuration

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

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the spotify mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Spotify's toolset — Troubleshooting, Debugging — is a fair guide to whether it matches your workflow. It is maintained by Naunau75; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Spotify's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.