Spotify MCP Server

Spotify playback control and library management for your AI assistant.

Data last scanned last week · Reviewed last month

39★ 609PythonMIT

Overview

This MCP server integrates your Spotify account with AI models, allowing direct control over music playback and library management. Through the Spotify Web API, it enables users to pause, skip, or resume tracks, search for specific media, and manage queues. Additionally, it supports creating and updating personal playlists directly through your AI interface. Setup requires creating an app via the Spotify Developer dashboard to obtain client credentials, which are then configured within your client's MCP settings.

Our verdict

With a security score of 39/100, this tool is classified as high-risk. The repository is explicitly marked as inactive with a notice that most pull requests will not be merged, and the lack of independent review for OAuth and read-only mode support introduces security uncertainty. Users should exercise extreme caution, as the maintainer is not actively updating the codebase, leaving it vulnerable to unpatched issues.

Supports playback, search, and playlist management
Zero direct dependencies reduces supply chain surface
Provides documented configuration steps for common clients
Licensed under the permissive MIT license

Project is officially marked as inactive by the maintainer
OAuth and read-only implementation lack security review
No official support or guarantee of future updates

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›Do I need a specific type of Spotify account to use this server?

Yes, you must have a Spotify Premium account, as it is required to use the Spotify developer API.

›What is the recommended method to prevent constant redirect URI prompts?

You can avoid the redirect URI prompt by cloning the repository and running the server locally via uv instead of using uvx.

›Where can I check if the MCP server encounters errors?

Logs are emitted to stderr; on macOS, these are typically found in ~/Library/Logs/Claude, while other platforms follow the standard MCP logs location.

›What are the configuration requirements for the Spotify developer dashboard?

You must create an app in your Spotify developer dashboard and set the redirect_uri to http://127.0.0.1:8080/callback.

›Is this project actively maintained?

As of March 2026, the project is marked as inactive and most pull requests will not be merged.