Spotify runs an official remote MCP server, and you can point Claude at it — but before you spend time on the setup, it’s worth knowing where it currently sits: gate’s directory tracks the endpoint as live, on a URL that reads external-pilot, with connectivity marked restricted. That’s a different situation from most servers in this series, and this guide covers what the server does, how to attempt a connection either directly or through a gateway, and why “official” and “open to everyone right now” aren’t the same claim here.
What the Spotify MCP server is for
Spotify’s server exposes music and podcast discovery as tools — the kind of thing you’d otherwise type into the Spotify search bar, reframed as a prompt to Claude:
- “Find something upbeat for a run, nothing I’ve played this week.”
- “What podcast episodes came out this week in the shows I follow?”
- “Recommend a few albums close to what I’ve been listening to lately.”
That’s a narrower surface than most servers in gate’s MCP server directory — it’s about recommendation and discovery, not account management, so there’s no playlist-editing or payment-adjacent tool call to worry about the way there is with, say, a banking or CRM server.
The catch: this endpoint is explicitly a pilot, not a general release
Most “allow-listed” servers in this series — Box, Figma, Dropbox — are fully released, and the restriction is narrower: the vendor only admits AI clients it has pre-approved, while the server itself is open to any account. Spotify’s situation reads differently. The endpoint URL itself names it as an external pilot, which is Spotify’s own signal that this isn’t a finished, generally available release yet. gate’s catalog marks it restricted for that reason, and in practice that can mean the OAuth step doesn’t complete for an account or client that isn’t part of the pilot — not because anything about your setup is wrong.
We don’t have visibility into which accounts or clients Spotify has admitted to the pilot, so treat any instructions below as “how to attempt it,” not a guarantee it completes on the first try. If you hit a wall at authorization, that’s the most likely explanation — see the unauthorized client error explained for the general pattern, and MCP OAuth scopes explained for why a server supporting OAuth in principle isn’t the same as every client being able to walk through it today. Pilots graduate to general availability on the vendor’s own schedule, so it’s worth checking back rather than assuming it’s permanently closed.
Option 1: Connect Spotify to Claude directly
If your account and client happen to be part of the pilot, the setup is the usual shape:
- Open Claude’s connector or MCP settings.
- Add a remote server pointing at Spotify’s MCP endpoint.
- Sign in with your Spotify account when prompted — standard OAuth, so Claude never sees your Spotify password, and you can revoke access from Spotify’s own account settings at any time.
Option 2: Connect it through a gateway
If you’re already connecting more than one MCP server, wiring each one directly into every AI client you use gets old fast — the connection sprawl covered in what an MCP gateway is. The pattern is to connect every server to one gateway URL, then point each AI client at that single URL instead of reconfiguring each pair separately. With gate, that means adding gate’s gateway URL to Claude once, then picking Spotify from the Spotify server page in the directory and attempting sign-in the same way you would directly. gate’s catalog tracks each server’s currently verified connectivity — including a pilot-stage case like this one — so you see the restriction before you spend time on the OAuth step, instead of finding out mid-flow.
What to check before you connect it
A recommendation tool is lower-stakes than most servers in this series, but a couple of things are still worth a look:
- What can it actually call? Don’t assume “music discovery” means read-only. Check the real tool list — gate’s free MCP security scanner lists every tool a server exposes, whether that’s a recommendation lookup or something that writes to your library or playlists.
- What does it see about your listening? Recommendation tools generally work by reading your listening history and taste profile, which is personal data even if it’s not financial or professional — worth knowing before you ask Claude to summarize “everything I’ve listened to this year” in a chat you might share.
- Is the server still there tomorrow? A pilot endpoint is more likely than a general-release one to change its URL, its tool list, or its own availability without much notice. If you connect through a gateway, that’s the kind of change drift detection is meant to catch — see how MCP rug pulls work.
Troubleshooting the connection
- OAuth fails or the sign-in screen never loads. Most likely the pilot restriction above — your account or client may not currently be part of it.
- Sign-in works but recommendations look generic. Spotify’s tools work from your existing listening history and preferences; a newer or less-used account will naturally get less personalized results, the same as it would in the Spotify app.
- The connection worked last week and doesn’t now. Pilot endpoints can change shape without the kind of advance notice a general-release product gives. Treat a sudden failure as a reason to re-check the server’s current status rather than assume your own setup broke.
The bottom line
Spotify’s MCP server is real and official, but gate’s directory currently tracks it as a restricted, pilot-stage endpoint rather than a general release — so the honest expectation going in is that it may not connect for every account or client yet, not that the setup steps above are wrong. If it does connect, the actual stakes are modest: a recommendation tool reading your listening history, not a tool that can move money or delete a shared file. Try it, expect the pilot wall is a real possibility, and check back as Spotify widens access.