Spotify MCP Server

MCP server connecting Claude with Spotify. This fork of varunneal/spotify-mcp adds smart-batching tools and advanced playlist features that optimize API usage. Its 25 documented tools cover playlist, tracks, info, playback. It runs locally over stdio via the published package.

People connecting API integration tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-07-30 · ★ 7 · #72 OF 250 MAINTAINED API INTEGRATION · VERIFIED 2026-08-25

MIT · Python servers · how we verify → /methodology

01 · Install Spotify

before you install - you'll need

Set SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REDIRECT_URI before connecting.

Claude Code

claude mcp add jamiew-spotify-mcp -- uvx spotify-mcp-jamiew

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "jamiew-spotify-mcp": {
      "command": "uvx",
      "args": [
        "spotify-mcp-jamiew"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

repository a fork of another project - check the upstream repo before trusting releases

license MIT - declared in the repository

pypi package spotify-mcp-jamiew - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.jamiew is GitHub-verified and matches the repo owner

03 · What Spotify can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can search tracks, albums, artists or playlists, with filters, move playback to another device, create a playlist, and rename a playlist or change its description/visibility.

Capability map

Tools grouped from the project's README - what Spotify lets an agent do.

read & search

10 tools - e.g. The signed-in user's profile; Search tracks, albums, artists or playlists, with filters; Track details, batched up to 50 per call

get_me · search_music · get_track_info · get_artist_info · get_album_info · get_playback_state…

Playlist

8 tools - e.g. Playlist metadata without its tracks; Playlist tracks, paginated to any size; Create a playlist

get_playlist_info · get_playlist_tracks · create_playlist · modify_playlist_details · add_tracks_to_playlist · remove_tracks_from_playlist…

Tracks

3 tools - e.g. Liked Songs, paginated; Like tracks; Unlike tracks

get_saved_tracks · save_tracks · remove_saved_tracks

Queue

2 tools - e.g. Now playing plus the upcoming queue; Queue a track

get_queue · add_to_queue

Control

1 tool - e.g. Play, pause, next, previous, seek, volume, shuffle, repeat

control_playback

Transfer

1 tool - e.g. Move playback to another device

transfer_playback

Latest releases

v0.4.1 · 2026-07-30

Fixes a broken install. mcp 2.0 removed mcp.server.fastmcp, which this server is built on, and the dependency had no upper bound - so a fresh uvx spotify-mcp-jamiew resolved mcp 2.x and crashed on import. uv.lock kept…

v0.4.0 · 2026-07-30

Nine new tools, a real playback control surface, and a fallback layer for the two Spotify API regimes that February 2026 split apps into. · Highlights · Playback split into read and write: playback_control becomes…

v0.3.1 · 2026-05-29

Fixes the MCP Registry publish from v0.3.0. · add the mcp-name: io.github.jamiew/spotify-mcp marker to the README so the registry can verify PyPI ownership · otherwise identical to v0.3.0 (first PyPI release - uvx…

04 · Who maintains Spotify

Spotify is maintained by jamiew. We track 2 MCP servers from jamiew - 2 actively maintained, 24 combined GitHub stars, oldest repo from Jan 2025. Full record: all servers from jamiew.

  1. Monarch MCP Server Access Monarch financial data - accounts, transactions, budgets, and more ★ 17

05 · Facts

category
API integration - ranked #72 of 250 actively-maintained API integration servers as of 2026-08-25.
release cadence
4 releases in the last 90 days (latest 2026-07-30)
registry
io.github.jamiew/spotify-mcp (active, first published 2026-05-29 · 3 versions)
packages
pypi:spotify-mcp-jamiew

06 · Spotify FAQ

Is Spotify still maintained?

Yes - as of 2026-08-25, its last commit was 2026-07-30 and it shipped 4 releases in the last 90 days. We re-verify nightly.

What can Spotify do?

With this server connected, an agent can search tracks, albums, artists or playlists, with filters, move playback to another device, create a playlist, and rename a playlist or change its description/visibility.

How do I install Spotify?

Run `uvx spotify-mcp-jamiew`. The README documents 3 environment variables (SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REDIRECT_URI) to set first. Set SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REDIRECT_URI before connecting. You can also paste the ready-made client config above.

Does Spotify run locally?

Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Spotify