Spotify MCP Server

Connect Claude to Spotify for music playback and management.

Local serverstdio 1

What is the Spotify MCP server?

Connect Claude to Spotify for music playback and management. That is what the spotify mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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
  • Manage, create, and update playlists

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Troubleshooting — Please open an issue if you can't get this MCP working. Here are some tips:

What it needs from you

Configuration is passed through the environment: SPOTIFY_REDIRECT_URI, SPOTIFY_CLIENT_ID, YOUR_CLIENT_ID, SPOTIFY_CLIENT_SECRET, YOUR_CLIENT_SECRET, UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

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.

How it compares

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 — is a fair guide to whether it matches your workflow. It is maintained by g2dgaming; 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.

Things to watch

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
TroubleshootingPlease open an issue if you can't get this MCP working. Here are some tips:

How to install the Spotify MCP server

{
  "mcpServers": {
    "spotify-3": {
      "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.

Configuration

VariableDescriptionRequired
SPOTIFY_REDIRECT_URIFilesystem location the server is allowed to use.Optional
SPOTIFY_CLIENT_IDConfiguration value read at startup.Optional
YOUR_CLIENT_IDConfiguration value read at startup.Optional
SPOTIFY_CLIENT_SECRETCredential the server authenticates with.Yes
YOUR_CLIENT_SECRETCredential the server authenticates with.Yes
UV_PUBLISH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Spotify to Troubleshooting.

Frequently asked questions

This MCP server allows you to control Spotify directly through Claude. You can play, pause, skip tracks, search for music, manage your queue, and get information about songs, albums, and playlists.