Reordering tracks, swapping the cover art, and building recommendations from seeds are all here, which puts it past the usual now-playing integrations. Setup asks for your own Spotify app credentials, and the OAuth redirect has to be the exact 127.0.0.1:8888/callback the server expects or authentication fails.
A server that authenticates against Spotify and exposes playback, search, playlist management and listening history as tools.
- auth-spotify runs the OAuth flow; search-spotify finds tracks, albums, artists or playlists
- Playback control — get-current-playback, play-track, pause-playback, next-track, previous-track
- Full playlist management — create-playlist, update-playlist, delete-playlist, add-tracks-to-playlist, remove-tracks-from-playlist, reorder-playlist-tracks
- get-playlist-cover and upload-playlist-cover manage the cover image, a base64 JPEG up to 256KB
- get-recommendations builds suggestions from seed tracks, artists or genres
- get-top-tracks over short_term, medium_term or long_term, and get-recently-played by timestamp
A Spotify account and API credentials — SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET from the Spotify Developer Dashboard, with http://127.0.0.1:8888/callback set as the redirect URI. Node.js 16 or higher; the repository ships prebuilt files, so the client can launch build/index.js directly. The access token is stored under ~/.spotify-mcp/tokens.json to persist between sessions.
One command plus a key — npx -y @smithery/cli install @imprvhub/mcp-claude-spotify --client claude, then supply credentials