Access Spotify data for songs, podcasts, artists, albums, playlists, and more through MCP.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Spotify.
The spotify MCP server exposes Spotify Data API content through a Model Context Protocol integration. Its documented scope includes songs, podcasts, artists, albums, playlists, and additional Spotify data. This makes it relevant for agent workflows that need to retrieve or work with information from Spotify's catalog rather than from a general-purpose data source.
The available description refers to millions of songs and podcasts, along with artist, album, and playlist data. It does not specify whether the server supports searching, retrieving individual records, creating or updating playlists, or performing other operations. Those details should be confirmed from the service documentation before building a workflow around a particular action.
The listed capability is access to the Spotify Data API. Based on the provided material, supported data areas include:
The spotify MCP server may be suitable when an MCP client needs Spotify catalog context, but the available information does not name individual MCP tools or describe their parameters and return formats. It also does not identify whether capabilities are read-only or include mutations. Developers should avoid assuming that playlist changes, playback control, recommendations, search, or user-library access are available unless the provider documents them separately.
No README is available for this listing, so implementation details are limited. There is no supplied information about the server's transport, authentication model, required credentials, installation commands, request limits, supported regions, or error behavior. These omissions do not establish that a feature is absent; they only mean it cannot be confirmed from the provided source material.
For evaluation, compare the application's required Spotify operations with the API methods exposed by the deployed service. If the application only needs catalog information about the listed content types, the spotify MCP server is a relevant candidate to investigate. If it needs account-specific data or write operations, verify those capabilities explicitly before adoption.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/spotify-2)<a href="https://allmcps.com/mcp/spotify-2"><img src="https://allmcps.com/api/badge/spotify-2?style=directory" alt="Spotify on AllMCPs" /></a>