Compared · spotify
9 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 9 have a source repository that is no longer publicly reachable.
Scope: 9 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Spotify Trends API | ai.trendsapi | no flag | REVIEW | 100 | remote endpoint |
| Spotify Trends MCP | ai.trendsmcp | no flag | REVIEW | 100 | remote endpoint |
| Spotify | io.github.jamiew | no flag | REVIEW | 85 | pypi spotify-mcp-jamiew |
| Spotify | io.github.pipeworx-io | no flag | REVIEW | 85 | remote endpoint |
| io.github.XavierFabregat/spotify-mcp | io.github.XavierFabregat | no flag | REVIEW | 79 | npm @xavifabregat/spotify-mcp |
| io.github.markswendsen-code/spotify | io.github.markswendsen-code | no flag | REVIEW | 71 | npm @striderlabs/mcp-spotify |
| io.github.khglynn/spotify-bulk-actions-mcp | io.github.khglynn | no flag | REVIEW | 64 | pypi spotify-bulk-actions-mcp |
| Spotify MCP by UnClick | io.github.malamutemayhem | repo unreachable | REVIEW | 92 | npm @unclick/spotify-mcp |
| Spotify | io.github.akutishevsky | repo unreachable | REVIEW | 80 | remote 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.