mcpbeat Sign in

Spotify MCP Server

answering

Spotify is answering right now. Last checked 11 min ago.

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
88 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Spotify every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp-gateway-external-pilot.spotify.net/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp-gateway-external-pilot.spotify.net/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp-gateway-external-pilot.spotify.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp-gateway-external-pilot.spotify.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp-gateway-external-pilot.spotify.net/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp-gateway-external-pilot.spotify.net/mcp streamable-http sign-in 56 ms 11 min ago

Alternatives to Spotify

same job, measured the same way
Shopify
by shopify
37 tools answering
Spotify
by pipeworx-io

Spotify MCP — Web API via client_credentials OAuth

208 installs/wk 50 tools answering
Spotify MCP by UnClick
by malamutemayhem

Spotify tools for spotify, music, playlists by UnClick.

52 installs/wk local only
Splice
by splice
answering
Spoonacular
by pipeworx-io

Spoonacular MCP.

200 installs/wk 62 tools answering
S
Sprouts
by sprouts
22 tools answering
Clarify
by clarify
answering
Netlify
by netlify
answering

Spotify — questions

Answers built from our own checks of this server.

Why is there no tool list for Spotify?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Spotify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 88 ms. The bar chart above shows every period we have measured.
How do I connect Spotify?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Spotify?
No API key is involved. Spotify answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Spotify?
It answers our handshake in 88 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.