Creativity · MCP — server

MCP Spotify Server

The MCP Spotify Server is a community-maintained Model Context Protocol server that wraps the Spotify Web API. Authenticated with an OAuth refresh token, it lets an LLM client search the catalog, control playback on active devices, and build or modify playlists on your account.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: search_tracks, play, pause, skip_next, add_to_playlist, create_playlist
Resources: spotify://playlist/{id} and spotify://track/{id} URIs
Auth: SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REFRESH_TOKEN env vars

Install

npx -y @modelcontextprotocol/server-spotify

Configuration

{
  "mcpServers": {
    "spotify": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-spotify"],
      "env": {
        "SPOTIFY_CLIENT_ID": "...",
        "SPOTIFY_CLIENT_SECRET": "...",
        "SPOTIFY_REFRESH_TOKEN": "..."
      }
    }
  }
}

Frequently asked questions

Is this server official?

No — it is community-maintained. Spotify does not publish an official MCP server; pick a well-maintained community repo.

Why does playback control sometimes fail?

Playback endpoints need an active Spotify device. Open the app on your desktop or phone so the API has a target to control.

What OAuth scopes should I request?

user-modify-playback-state, user-read-playback-state, playlist-modify-private, and playlist-modify-public cover the common tools.

Sources

Spotify Web API — accessed 2026-04-20
MCP servers index — accessed 2026-04-20