6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search Spotify, build playlists and manage your library via an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Spotify MCP server connects a Spotify account to Claude and other MCP clients. An agent can search the catalogue for music and podcasts, look up specific tracks, see what you are playing right now, build a playlist, and add things to or remove things from your saved library. Spotify hosts it, and each listener authenticates with their own account.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Remove_from_library has no documented undo. It removes tracks, albums, episodes, shows, audiobooks, playlists and users, up to 40 URIs per call. Spotify's documented recovery is a 90-day restore for deleted playlists only; for a missing library item its advice is to search and save it again.mcp-gateway-external-pilot.spotify.net says so in the hostname, on a .net domain. Expect it to be capable of moving or being withdrawn. Spotify publishes no stability commitment for it that we could find.public to true; the connector was granted only playlist-modify-private. The scope evidence points to private, and no Spotify document states what the tool sends. Check the first playlist an agent makes.get_currently_playing reads live state. Current item, progress, and a device object with name, type, volume and private-session flag.readOnlyHint or destructiveHint value we can report. Treat all six as unannotated.no_auth and is_authless: true; the server returns 401 and demands a bearer token.registration_endpoint, so an arbitrary client cannot self-register against this endpoint.It searches Spotify's catalogue, builds playlists and changes what is saved in your library. The six listed tools cover catalogue search, looking up specific tracks, reading what is playing right now, creating a playlist, and adding to or removing from your saved library. Spotify markets it as music and podcast recommendations that draw on your listening history.
It removes saved items, and Spotify documents no undo for them. The matching Web API operation accepts up to 40 Spotify URIs at once spanning tracks, albums, episodes, shows, audiobooks, playlists and users. Spotify's guidance for a missing library item is to search for it and save it again. Only deleted playlists have a documented recovery path, lasting 90 days.
Spotify's API defaults new playlists to public, but this connector was granted only `playlist-modify-private`. Spotify's specification states the `public` field defaults to true and that creating a private playlist requires that scope. The connector holds the private scope and not the public one, which points to private creation. Spotify publishes no MCP tool reference confirming what the tool sends.
No, Free accounts work. Spotify states both Free and Premium listeners can use the Claude integration, and that Premium users additionally get a playlist generated from a described vibe or mood. The gating is real but partial. Every playback-control operation in Spotify's Web API is documented as Premium-only, so anything that starts, pauses or skips audio needs a subscription.
No tool in the listing does that, but the granted scopes allow it. None of the six names covers pause, skip, seek, volume or queue. Yet the connector requests `user-modify-playback-state` and `app-remote-control`, which Spotify defines as write access to playback state and remote control of the Spotify app. The grant is wider than the tool list.
Your live listening state, and the device playing it. The matching Web API operation returns the current track or episode, progress in milliseconds, whether playback is running, shuffle and repeat settings, and a device object naming the hardware, its type, volume and whether it is in a private session. That is a real-time picture of what you are doing now.
Six, against 96 operations in Spotify's published Web API specification. The connector leaves out the entire player family, queue management, follow and unfollow, playlist editing after creation, and listening history. That is a deliberately narrow surface over a large API, and narrowing is the right instinct. The scope grant does not narrow with it.
public default and its scope requirement; the collaborative-playlist requirement; the playback-state response and device schema; catalogue search and its scope-free security block; bulk track lookup with its 50-ID cap; the Premium-only sentence on ten player operations. Spotify's robots.txt explicitly allows crawling this file.user-library-modify and user-follow-modify, and the Premium note on streaming.no_auth posture our probe contradicts. Snapshot dated 2026-08-16. · retrieved 2026-08-16initialize POST to the endpoint; three RFC 9728 path forms; two RFC 8414 path forms on the resource host; authorization-server metadata at accounts.spotify.com. No authentication was performed and no tool was called. · retrieved 2026-08-19Connect Spotify once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.