mcp-spotify
MCP ServerFreeMCP server: mcp-spotify
Capabilities5 decomposed
spotify playback control via mcp protocol
Medium confidenceEnables AI agents and LLM-based applications to control Spotify playback (play, pause, skip, volume adjustment) through the Model Context Protocol, which standardizes tool calling between AI clients and servers. The MCP server acts as a bridge that translates tool invocations from Claude or other MCP-compatible clients into Spotify Web API calls, handling OAuth2 authentication and session management transparently.
Implements Spotify control as a native MCP tool rather than a custom REST wrapper, enabling seamless integration into Claude's tool-calling ecosystem without requiring developers to write MCP protocol boilerplate themselves
Simpler than building custom Spotify API integrations because MCP handles the client-server protocol contract; more standardized than direct API calls because it works with any MCP-compatible AI client, not just one platform
spotify track and artist search via semantic tool calling
Medium confidenceAllows AI agents to search Spotify's catalog for tracks, artists, and playlists by translating natural language queries into structured Spotify Search API calls through MCP tool invocations. The server accepts free-form search strings and optional filters (artist, album, type) and returns paginated results with metadata (track duration, popularity, preview URLs, artist info).
Wraps Spotify's Search API as an MCP tool, enabling AI agents to perform structured searches without developers implementing search UI logic — the agent handles query interpretation and result filtering
More flexible than hardcoded playlists because it searches Spotify's full catalog dynamically; more natural than REST API calls because the agent can interpret conversational search intent and retry with different query terms
current playback state retrieval and device discovery
Medium confidenceProvides AI agents with real-time visibility into the user's current Spotify playback state (currently playing track, progress, device info, repeat/shuffle modes) and available playback devices through MCP tool calls. The server queries Spotify's Currently Playing and Available Devices endpoints, caching results briefly to reduce API calls while maintaining freshness for agent decision-making.
Exposes Spotify's playback state as queryable MCP tools rather than requiring agents to maintain their own state model, enabling stateless agent design where each decision is based on fresh API data
More reliable than client-side state tracking because it always reflects server truth; more efficient than polling because MCP clients can call on-demand rather than continuously syncing
user profile and saved tracks retrieval
Medium confidenceEnables AI agents to access authenticated user's Spotify profile information (display name, follower count, subscription tier) and retrieve their saved/liked tracks library through MCP tool calls. The server implements pagination for the saved tracks endpoint, allowing agents to browse the user's music library and make recommendations based on their existing preferences.
Exposes user library data as MCP tools, allowing agents to build context about user preferences without requiring custom database storage — the agent can query Spotify as a knowledge source
More current than cached user preference data because it queries live Spotify library; more privacy-preserving than storing user music history locally because data stays in Spotify's ecosystem
mcp protocol server implementation with oauth2 flow
Medium confidenceImplements a complete MCP server that handles the Model Context Protocol handshake, tool schema registration, and request/response marshaling for all Spotify capabilities. The server manages OAuth2 authentication flows (authorization code grant), token refresh, and secure credential storage, exposing Spotify operations as standardized MCP tools that Claude and other MCP clients can discover and invoke.
Provides a complete, working MCP server implementation rather than just API wrapper code, handling protocol details (tool registration, schema validation, error marshaling) that developers would otherwise need to implement themselves
Simpler than building MCP servers from scratch because it includes OAuth2 flow and token management; more standardized than custom REST wrappers because it follows MCP specification for tool discovery and invocation
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with mcp-spotify, ranked by overlap. Discovered automatically through the match graph.
Spotify Player
Control Spotify playback, queue, volume and playlists from Claude/Cursor via MCP. (Python)
spotify-mcp-server
MCP server: spotify-mcp-server
Spotify Server
Access Spotify's music catalog and interact with tracks, albums, and artists.
Spotify
Spotify Web API. Browse music, manage playlists, control playback, and explore listening history.
Moodify
Moodify uses Spotify's secure API to find and suggest the best tracks to fit your...
spotify-mcp-py
MCP server: spotify-mcp-py
Best For
- ✓AI agent developers building conversational music control interfaces
- ✓Teams integrating Spotify into Claude-powered applications
- ✓Builders prototyping voice assistants with music playback capabilities
- ✓Music discovery applications powered by AI agents
- ✓Conversational music search interfaces (voice or text-based)
- ✓Recommendation systems that need to validate track availability before suggesting
- ✓Context-aware AI music assistants that need playback state before taking action
- ✓Multi-device Spotify setups where agents must target specific speakers or devices
Known Limitations
- ⚠Requires active Spotify Premium account — free tier accounts cannot use Web API playback controls
- ⚠MCP protocol overhead adds ~100-200ms latency per command compared to direct REST API calls
- ⚠No support for queue manipulation or playlist reordering — only basic playback state control
- ⚠Depends on Spotify Web API rate limits (429 responses when exceeded)
- ⚠Search results limited to 50 items per query — pagination requires multiple tool calls
- ⚠No fuzzy matching for misspelled artist/track names — relies on Spotify's built-in search algorithm
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
About
MCP server: mcp-spotify
Categories
Alternatives to mcp-spotify
Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs
Compare →AI-optimized web search and content extraction via Tavily MCP.
Compare →Scrape websites and extract structured data via Firecrawl MCP.
Compare →Are you the builder of mcp-spotify?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →