
Spotify
io.github.jamiewPublished by GitHub account jamiewv0.9.2Updated Nov 7, 2026
MCP server connecting LLMs to Spotify, with smart-batching and large-playlist tools
Overview
Local MCP server that lets an assistant search Spotify, control playback, and manage playlists, Liked Songs, and saved media on your account.
- What you can do
- Search and read catalog data: tracks, albums, artists, playlists, shows, episodes, audiobooks, top items, and recently played
- Control playback: play, pause, skip, seek, volume, shuffle, repeat, queue, and move between Spotify Connect devices
- Manage playlists: list, read tracks, create, rename, change visibility, add, remove, reorder, follow and unfollow
- Manage your library: save, remove, and check Liked Songs, albums, artists, shows, episodes, and audiobooks
- Read your profile and current playback state
- When to use it
- Useful when you want an assistant to act on your own Spotify account: finding music, building or cleaning up playlists, curating Liked Songs, or driving playback on a chosen device from a chat client.
- Requirements
- Runs locally over stdio via uvx (Python 3.12+ and uv). Needs a Spotify developer app with the redirect URI registered, plus SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, and SPOTIFY_REDIRECT_URI set in the client config. First use opens a browser for OAuth; playback requires Spotify Premium and an active Spotify Connect device.
Installation
In SourceWeft
- Open Spotify in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[Spotify MCP, Python local server]
spotify-mcp
mcp-name: io.github.jamiew/spotify-mcp
A local Python MCP server for searching Spotify, controlling playback, and managing playlists and Liked Songs from your MCP client. Runs over stdio with your Spotify account. This is a supported fork of varunneal/spotify-mcp.
The TypeScript edition supports local and hosted use, with a different MCP surface.
Setup
Requires Python 3.12+, uv, and Spotify Premium for playback.
- Create an app in the Spotify developer dashboard.
- Register
http://127.0.0.1:8888as its redirect URI, exactly as written. - Copy the app's Client ID and Client Secret into your MCP client's configuration:
Restart the client. On first use, a browser opens for Spotify authorization; the token is cached locally. Keep the client secret and token cache private. Playback needs an available Spotify Connect device, so open Spotify on the device you want to control.
Client-specific setup: Claude Desktop, Claude Code, and Codex. Use the same command and environment variables in each client's format.
Run from source
The package command above uses the published package, which may lag this README's source changes. To run the current checkout:
In the config above, change command to uv and args to
["--directory", "/absolute/path/to/spotify-mcp", "run", "spotify-mcp"].
Keep the same environment variables. Without cloning, use
uvx --from git+https://github.com/jamiew/spotify-mcp.git spotify-mcp.
Reauthorization: artist-follow checks need user-follow-read, and following or
unfollowing artists and playlists needs user-follow-modify. Existing grants do not
receive new scopes automatically. Restart and complete Spotify authorization when prompted;
if access is still denied, review the app's grant in your Spotify account and reauthorize.
Do not automatically delete the auth cache.
Features
48 tools, six resources (user, playback, track, playlist, artist, album), and five prompts. Tools provide typed outputs and behavior annotations; large playlist reads report progress. Playlist removal asks for confirmation where supported, reordering uses snapshot guards, and playback control attempts best-effort read-after-write confirmation, not guaranteed success.
Tools
Behavior to know
- New playlists default to private. Existing playlists are unchanged. Spotify can report unexpected visibility, so confirm sensitive playlists in the Spotify app.
- Library writes (tracks, artists, shows, episodes, audiobooks) and membership checks accept 50 items, sent upstream in batches of 40. Album saves, removals and checks accept 20. Membership results preserve input alignment; incomplete chunks fail. Writes are not atomic across chunks: earlier changes may remain after an error. Check membership before retrying.
- Restricted apps cap search pages at 10. Advance by the returned
offset + limit, not the requested size. Individual-track fallback can make up to 50 Spotify requests. - Playlist pagination counts positions, including unresolved rows and local files with
id: null. Local files also setis_local; positions remain valid for reordering.
Spotify access and policy
- Permissions and app access mode determine available endpoints and playlist access. A 403 may mean missing permission, not a retired endpoint. Existing integrations' February restrictions were postponed; restricted apps use the February 2026 API routes.
- Development Mode normally allows five allowlisted users and requires a Premium app owner; older larger allowlists may be grandfathered. Extended access is not routine hobby-project approval: criteria include an organization, a legal entity, a launched service, and 250,000 monthly active users. A public URL does not remove these limits.
- All Development Mode apps on a developer account share one quota, even with the
25 permitted Client IDs.
This server surfaces 429 errors without retries, including
QUOTA_EXCEEDEDand ordinary rate limits withRetry-Afterwhen provided. No guaranteed quota reset time is specified. - This server uses one local identity. Do not share its token cache or expose it as an unauthenticated public service. Other users should self-host and authorize their own accounts.
- AI policy is a separate constraint. Spotify Developer Policy III.14 restricts training or otherwise ingesting Spotify Content into AI/ML models; "no training" or "metadata only" is not automatic clearance. III.13 restricts analysis and derived metrics; III.3 restricts voice-control assistants. Seek Spotify clarification or approval before public AI access. This is a risk notice, not legal advice or permission.
Moving between implementations
Shared versions and tool names do not imply drop-in compatibility with other implementations. Check arguments, limits, and result shapes before switching. Preserve any workflow that relies on this server's resources, five prompts, snapshot guards, removal confirmation, or playback confirmation; those behaviors are not universal.
Credits
MIT license, copyright 2025 Varun Neal Srivastava. Thanks to @varunneal for the original project, @jamiew, @jonico, @tedeuxx, and @karimStekelenburg.
Banner made with Glif.
Source: README.md at commit c544333
Tools
0Version history
6- v0.9.2LatestNov 7, 2026
- v0.8.1Nov 3, 2026
- v0.7.0Sep 20, 2026
- v0.6.1Sep 18, 2026
- v0.6.0Sep 17, 2026
- v0.4.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts