Spotify

What marcelmarais/Spotify does

marcelmarais/Spotify gives an MCP client access to selected Spotify account and playback operations. It can search for tracks, albums, artists, and playlists, then use Spotify IDs or URIs to start playback. Account-oriented tools expose the user’s playlists, playlist contents, Liked Songs, followed artists, recently played tracks, current queue, and available Spotify Connect devices.

The write operations cover common listening and playlist workflows: play, pause, resume, skip forward, skip backward, add an item to the queue, create a playlist, add tracks to an existing playlist, and remove tracks from Liked Songs. Playlist creation accepts a name, optional description, and public/private setting.

How it works

The server communicates with Spotify through the Spotify API and presents the operations as MCP tools for an AI assistant. Search results include item identifiers and descriptive details, which can then be passed to playback or playlist tools. Playback can target a device when a device ID is supplied; otherwise, the active playback context is used for operations such as pausing, resuming, and skipping.

Read tools support pagination or result limits where Spotify collections can be large. For example, playlist tracks and saved tracks use limit and offset values, while followed artists can continue from a cursor returned by an earlier request. Queue results can be limited to a chosen number of upcoming items.

Setup and configuration

Using the server requires a Spotify Developer application and Spotify API configuration, followed by the authentication process described by the project. The repository documents installation and setup for MCP clients, including Claude Desktop, Cursor, and VS Code with Cline.

Deployment options include a standard local client setup, Streamable HTTP, OAuth-capable clients such as MCPHub, and Docker. Docker is documented as an option for MCPHub deployments. The client configuration must point to the server using the transport appropriate to the chosen setup.

Tools and capabilities

The documented tool groups include:

• Search Spotify’s catalog by track, album, artist, or playlist.
• Inspect current playback, including track, progress, device, volume, shuffle, and repeat state.
• List user playlists and retrieve tracks from a selected playlist.
• Read recently played tracks, saved tracks, followed artists, the playback queue, and available devices.
• Remove tracks from Liked Songs, with up to 40 track IDs per request.
• Start playback for a track, album, artist, or playlist, optionally on a selected device.
• Pause, resume, skip to the next track, or return to the previous track.
• Create playlists and add track URIs or IDs at an optional position.
• Add a track, album, artist, or playlist to the current queue.

Limitations and notes

Playback and account operations depend on Spotify authentication and the user’s available Spotify Connect devices. Several collection tools return bounded pages, so assistants may need multiple calls with offsets or cursors to process larger libraries. Search results are limited to the requested result range, and removing saved tracks accepts no more than 40 IDs in one request.