Spotify
Let your coding agent search, browse, and manage Spotify playlists and library without leaving the chat.
Overview
Spotify MCP is a MCP server for the Build phase that connects LLMs to Spotify with OAuth, smart-batching, and large-playlist tools.
What is this MCP server?
- Stdio MCP package spotify-mcp-jamiew v0.3.1 via uvx from PyPI
- OAuth with SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, and SPOTIFY_REDIRECT_URI (default http://127.0.0.1:8888)
- Smart-batching and tools tuned for large playlists so agents do not choke on huge libraries
- Bridges LLM agents to Spotify Web API workflows from developer.spotify.com apps
- Server version 0.3.1 on PyPI identifier spotify-mcp-jamiew
- 3 environment variables (2 secrets required plus redirect URI)
- stdio transport with uvx runtime hint
Community signal: 7 GitHub stars.
What problem does it solve?
Agents cannot touch your Spotify account or huge playlists without brittle one-off API scripts and token handling.
Who is it for?
Indie builders shipping agent workflows, playlist utilities, or creative tools that need live Spotify data.
Skip if: Teams that only need a static embed widget with no agent access, or anyone unwilling to run OAuth on localhost.
What do I get? / Deliverables
After you register the MCP with your Spotify app secrets, your agent can query and manipulate Spotify data through standardized tools.
- Registered stdio MCP server in your agent host
- OAuth-authenticated Spotify tool calls from the agent
- Batch-friendly access patterns for large playlists
Recommended MCP Servers
Journey fit
Spotify wiring is an external API integration you add while building agent-powered or music-adjacent products. OAuth credentials and stdio MCP fit the integrations shelf where solo builders connect third-party services to Claude Code or Cursor.
How it compares
MCP integration to Spotify Web API, not a standalone DJ app or skills.sh workflow skill.
Common Questions / FAQ
Who is Spotify MCP for?
Solo builders and small teams who use Claude Code, Cursor, or other MCP hosts and want Spotify library and playlist operations inside the agent.
When should I use Spotify MCP?
Use it during Build when you are wiring music discovery, playlist automation, or catalog features into an agent-backed product.
How do I add Spotify MCP to my agent?
Create a Spotify Developer app, set SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET, match SPOTIFY_REDIRECT_URI, then launch the stdio server with uvx spotify-mcp-jamiew and register it in your MCP client config.