spotify-pp-mcp — MCP server for Spotify playback control via Claude
draft — generated, polish on first use.
Category: pp-mcp Where it works: Claude Code / both Source: ~/.mcp.json
What it is
MCP server that exposes Spotify playback and library tools to Claude. Runs locally as a remote/Go process; tool surface is not introspectable from the host.
How to trigger it
- “play <track/artist/playlist>”
- “pause spotify”
- “what’s playing”
- “skip this”
- “add this to my queue”
- Direct command: none known — use natural language.
How to use it
Operator states a playback or library intent in plain language. The MCP server receives the request, executes it against the user’s Spotify account, and returns confirmation or current state.
Practical examples
- you: “play my Discover Weekly” → Spotify starts the playlist; Claude confirms “Now playing Discover Weekly”.
- you: “what’s currently playing” → MCP returns track title, artist, and playback status.
Tools
| tool | what it does | example |
|---|---|---|
| play | starts playback of track/artist/playlist/uri | play “Bohemian Rhapsody” |
| pause | pauses current playback | pause |
| resume | resumes paused playback | resume |
| skip | skips to next track | skip |
| previous | returns to previous track | previous |
| now_playing | returns current track info | now_playing |
| search | searches Spotify catalog | search “jazz piano” |
| queue | adds item to play queue | queue “track:xyz” |
| devices | lists available Spotify devices | devices |
| transfer | transfers playback to another device | transfer “Living Room” |
Notes / limits
Remote/Go binary — tool list is inferred from standard Spotify Web API patterns, not verified against running instance. Requires valid Spotify auth token; playback only works on devices already logged into the same account.