Overview
What is Spotify MCP Server?
A lightweight Model Context Protocol (MCP) server that enables AI assistants like Cursor and Claude to control Spotify playback and manage playlists. It uses the Spotify Web API and requires a Spotify Premium account.
How to use Spotify MCP Server?
Clone the repository, run npm install && npm run build, then configure a Spotify Developer application and run npm run auth to obtain OAuth tokens. Add the server to Claude Desktop or Cursor settings using the node build/index.js command path.
Key features of Spotify MCP Server
- Read Spotify data: search tracks, albums, artists, playlists.
- Get currently playing track and user playlists.
- Retrieve playlist tracks with metadata.
- Control playback: play, pause, skip to next/previous.
- Create and add tracks to playlists.
Use cases of Spotify MCP Server
- Ask an AI assistant to play a specific song, album, or artist.
- Create new playlists from natural language descriptions.
- Copy tracks between playlists via voice or text commands.
- Query currently playing track and playback progress.
FAQ from Spotify MCP Server
What runtime does Spotify MCP Server require?
Node.js v16 or higher.
Does it require a Spotify Premium subscription?
Yes, a Spotify Premium account is required to control playback.
How is authentication handled?
The server uses OAuth 2.0. Run npm run auth to generate an authorization URL, then the server automatically exchanges the code for access and refresh tokens, which are stored in a spotify-config.json file.
Where are the Spotify API credentials configured?
In a spotify-config.json file in the project root, containing your clientId, clientSecret, redirectUri, and later the tokens.
What transport does the server use?
The server is configured as a stdio‑based MCP server; it is launched via node build/index.js in Claude Desktop or Cursor MCP settings. No authentication or transport beyond the OAuth tokens is needed for the MCP connection itself.
