Spotify
Give your agent full Spotify Web API coverage for playlists, playback, search, and library workflows while you build music-adjacent products.
Overview
Spotify MCP is a MCP server for the Build phase that exposes Spotify Web API albums, artists, playlists, and player controls to your agent.
What is this MCP server?
- Remote streamable-http MCP at https://sptfy-mcp.online/mcp
- Advertises full Spotify Web API coverage: albums, artists, playlists, player controls, and more
- Server version 1.0.0; GitHub source spotify-mcp under akutishevsky
- Hosted endpoint so agents with HTTP MCP avoid running a local Spotify OAuth stack in v1 catalog metadata
- Useful for prototyping DJ workflows, focus playlists, or app features without writing every API wrapper by hand
- 1 remote endpoint: https://sptfy-mcp.online/mcp (streamable-http)
- GitHub repository akutishevsky/spotify-mcp
What problem does it solve?
Building or testing Spotify-powered features forces repetitive API exploration and player experiments outside the agent session.
Who is it for?
Indie developers prototyping Spotify integrations, playlist automation, or player demos inside MCP-capable agents.
Skip if: Production apps that need guaranteed SLA without reviewing the hosted bridge, or teams blocked from third-party music API proxies by policy.
What do I get? / Deliverables
After connecting the remote MCP URL, your agent can orchestrate Spotify library and playback operations aligned with Web API coverage described in the server listing.
- Agent-callable Spotify albums, artists, playlists, and player operations
- Faster integration prototypes against Spotify Web API surfaces
- Remote MCP connection to https://sptfy-mcp.online/mcp v1.0.0
Recommended MCP Servers
Journey fit
Spotify Web API access is primarily an integration-building concern when you prototype player features, bots, or creative tooling. Integrations is the canonical shelf for third-party API bridges like albums, artists, playlists, and player controls exposed over MCP.
How it compares
Spotify Web API MCP bridge, not an official Spotify developer SDK replacement or music production skill.
Common Questions / FAQ
Who is Spotify MCP for?
It is for builders and solo developers who want agent-driven access to Spotify albums, artists, playlists, and player APIs over MCP.
When should I use Spotify MCP?
Use it during build-phase integration spikes when you need fast playlist, search, and playback experiments before committing to a custom Spotify client.
How do I add Spotify MCP to my agent?
Add a remote MCP server entry for https://sptfy-mcp.online/mcp with streamable-http transport and complete any Spotify auth steps your client or the service documentation requires.