← Index
Compared · spotify

8 Spotify MCP servers. Which one to use.

Every Spotify server we index, with whether its source is still reachable and whether we hold a screening verdict. 2 of 8 have a source repository that is no longer publicly reachable.

Scope: 8 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.

ServerPublisherSourceScreenedQualityInstall
Spotify Trends MCPai.trendsmcpno flagREVIEW90remote endpoint
Spotifyio.github.pipeworx-iono flagREVIEW87remote endpoint
Spotifyio.github.jamiewno flagREVIEW83pypi spotify-mcp-jamiew
io.github.XavierFabregat/spotify-mcpio.github.XavierFabregatno flagREVIEW80npm @xavifabregat/spotify-mcp
io.github.markswendsen-code/spotifyio.github.markswendsen-codeno flagREVIEW72npm @striderlabs/mcp-spotify
io.github.khglynn/spotify-bulk-actions-mcpio.github.khglynnno flagREVIEW65pypi spotify-bulk-actions-mcp
Spotify MCP by UnClickio.github.malamutemayhemrepo unreachablenot screened93npm @unclick/spotify-mcp
Spotifyio.github.akutishevskyrepo unreachableREVIEW82remote endpoint

“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.