
Spotify
- Updated March 11, 2026
- markswendsen-code/mcp-spotify
io.github.markswendsen-code/spotify is a MCP server that lets AI agents search Spotify, control playback, and manage playlists over stdio.
About
io.github.markswendsen-code/spotify is a Model Context Protocol server that connects AI coding agents to Spotify so you can search tracks, adjust playback, and maintain playlists through natural language instead of switching to the Spotify app. developers who live in Claude Code, Cursor, or Codex often want small quality-of-life integrations that make demos, focus sessions, or voice-driven workflows smoother without building a custom Spotify OAuth client by hand. You reach for this server during the build phase when you are wiring MCP integrations into your agent config: install the npm package, register stdio transport, and supply Spotify API credentials. It is not a music analytics platform or a production streaming backend; it is a thin MCP bridge. Version 0.1.0 signals an early package, so expect to verify scopes and rate limits against your Spotify developer app before relying on it in daily use.
- stdio MCP server published as @striderlabs/mcp-spotify on npm (v0.1.0)
- Search music and manage playlists from agent tool calls
- Control playback (play, pause, skip) through Spotify’s API
- GitHub source at markswendsen-code/mcp-spotify
- Designed for Claude Code–style agents that need ambient or demo music control
Spotify by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add spotify -- npx -y @striderlabs/mcp-spotifyAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @striderlabs/mcp-spotify |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | March 11, 2026 |
| Repository | markswendsen-code/mcp-spotify ↗ |
What it does
Wire your coding agent to search Spotify, control playback, and manage playlists without leaving the terminal.
Who is it for?
Best when you're personalizing agent setups with Spotify for focus music, demos, or assistant-driven playlist edits.
Skip if: Skip if you need licensed streaming in a customer-facing SaaS product without building your own Spotify compliance story.
What you get
After you register the stdio server, your agent can search, play, and curate playlists through MCP tools instead of manual app juggling.
- Registered stdio MCP server entry pointing at @striderlabs/mcp-spotify
- Agent-callable tools for search, playback control, and playlist management
- Repeatable local workflow for music actions from the coding agent
By the numbers
- Server version 0.1.0 in MCP server schema
- npm package identifier @striderlabs/mcp-spotify
- Transport type stdio
README.md
@striderlabs/mcp-spotify
MCP server for Spotify — let AI agents search music, control playback, and manage playlists via the Spotify Web API.
Built by Strider Labs.
Features
- Search — Find tracks, artists, albums, and playlists
- Playlists — View, create, and edit your playlists
- Playback Control — Play, pause, skip, go back, set volume
- Multi-device — List and switch between Spotify Connect devices
- OAuth 2.0 — Secure authorization with PKCE (no client secret needed)
- Token persistence — Tokens stored locally, auto-refreshed
Setup
1. Create a Spotify App
- Go to the Spotify Developer Dashboard
- Click Create App
- Set Redirect URI to:
http://localhost:8888/callback - Copy your Client ID
2. Install
npx @striderlabs/mcp-spotify
Or install globally:
npm install -g @striderlabs/mcp-spotify
3. Configure Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"spotify": {
"command": "npx",
"args": ["-y", "@striderlabs/mcp-spotify"],
"env": {
"SPOTIFY_CLIENT_ID": "your_client_id_here"
}
}
}
}
4. Authenticate
In Claude, call the auth tool once:
spotify_auth
A browser window will open for you to authorize access. After approving, tokens are saved locally at ~/.striderlabs/spotify/tokens.json and auto-refreshed.
Environment Variables
| Variable | Required | Description |
|---|---|---|
SPOTIFY_CLIENT_ID |
Yes | Your Spotify app's Client ID |
Tools
Authentication
| Tool | Description |
|---|---|
spotify_status |
Check connection status and logged-in account |
spotify_auth |
Authorize via browser (OAuth 2.0 PKCE) |
spotify_logout |
Clear stored tokens |
Search
| Tool | Parameters | Description |
|---|---|---|
search_tracks |
query, limit? |
Search for songs |
search_artists |
query, limit? |
Search for artists |
search_albums |
query, limit? |
Search for albums |
search_playlists |
query, limit? |
Search for playlists |
Playlists
| Tool | Parameters | Description |
|---|---|---|
get_playlists |
limit? |
Get your playlists |
create_playlist |
name, description?, public? |
Create a new playlist |
add_to_playlist |
playlistId, uris[], position? |
Add tracks |
remove_from_playlist |
playlistId, uris[] |
Remove tracks |
Playback
| Tool | Parameters | Description |
|---|---|---|
get_currently_playing |
— | Current track, progress, device |
play |
deviceId?, contextUri?, uris?[], offsetPosition?, positionMs? |
Start/resume playback |
pause |
deviceId? |
Pause playback |
next_track |
deviceId? |
Skip to next track |
previous_track |
deviceId? |
Go to previous track |
set_volume |
volumePercent, deviceId? |
Set volume (0–100) |
get_devices |
— | List Spotify Connect devices |
transfer_playback |
deviceId, play? |
Switch playback device |
Example Workflow
1. spotify_status → check if authenticated
2. spotify_auth → open browser to authorize (first time)
3. search_tracks query="Bohemian Rhapsody"
4. get_devices → list available devices
5. play uris=["spotify:track:..."] deviceId="..."
6. get_currently_playing → see what's playing
7. set_volume volumePercent=70
8. next_track → skip to next
9. get_playlists → see your playlists
10. create_playlist name="AI Picks"
11. add_to_playlist playlistId="..." uris=["spotify:track:..."]
Requirements
- Node.js 18+
- Spotify account (Free or Premium)
- Spotify Premium required for: volume control, playback control
Technical Details
- Protocol: Model Context Protocol (MCP) over stdio
- Auth: OAuth 2.0 Authorization Code with PKCE
- API: Spotify Web API v1
- Token storage:
~/.striderlabs/spotify/tokens.json - Browser automation: Playwright (for OAuth browser launch)
License
MIT — Strider Labs
Recommended MCP Servers
How it compares
Spotify MCP integration for agents, not a DAW plugin or music recommendation skill.
FAQ
Who is io.github.markswendsen-code/spotify for?
Developers using Claude Code, Cursor, or Codex who want Spotify search and playback as MCP tools during development.
When should I use io.github.markswendsen-code/spotify?
Use it while configuring build-phase agent integrations when you want music control callable from the same session as your code agent.
How do I add io.github.markswendsen-code/spotify to my agent?
Install @striderlabs/mcp-spotify from npm, configure stdio MCP in your client, and provide valid Spotify API or OAuth credentials per the repo README.