Files and knowledge
Spotify for AI agents.
Managed auth, ready-made tools.
Search music, read and build playlists, and control playback in Spotify on behalf of each of your users.
About Spotify
With the Spotify connector, your agent works with each user’s own Spotify account. It can search the catalog, list playlists, create a playlist and add tracks, see what is playing, read recently played tracks and start or pause playback, using only the tools your project allows.
Spotify is a music and podcast streaming service.
Tools
What your agent can do in Spotify.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Spotify connection.
-
Search
Readspotify_searchSearch for tracks, albums, artists, playlists and shows.
-
List playlists
Readspotify_list_playlistsList the user's playlists.
-
Create a playlist
Writespotify_create_playlistCreate a new playlist.
-
Add tracks to a playlist
Writespotify_add_tracksAdd tracks to a playlist.
-
Get the playing track
Readspotify_get_playingSee what is playing on the user's account.
-
List recently played
Readspotify_list_recently_playedList the tracks the user played recently.
-
Start playback
Writespotify_start_playbackStart or resume playback on an active device.
-
Pause playback
Writespotify_pause_playbackPause playback on an active device.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Spotify, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent search and control playback, and switch off
spotify_create_playlistso it can never add playlists to the account. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example playback but not playlists. A call outside them is refused.
Get started
Connect Spotify
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Spotify
Each end user authorizes their own Spotify account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Spotify account, once. const connection = await agent200 .user("user_123") .connect("spotify"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Spotify tools
Name the user, the model and the tools. The model decides which Spotify tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Make a playlist of upbeat songs for my run", tools: ["spotify"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Spotify's own sign-in page. You never see or store their Spotify password.
-
What access is requested
The scopes the connection needs, such as reading playlists, editing playlists or controlling playback, listed on Spotify's authorization screen. Users can remove the app later from their Spotify account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Spotify connector and how to use it.
Connector: Spotify, through Agent200. In code: "spotify". What it does: Search music, read and build playlists, and control playback in Spotify on behalf of each of your users. Page: https://www.agent200.com/connectors/spotify/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Spotify's own page, through the authorization link Agent200 returns. Never ask a user for a Spotify password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: spotify_search, spotify_list_playlists, spotify_get_playing, spotify_list_recently_played. Write tools: spotify_create_playlist, spotify_add_tracks, spotify_start_playback, spotify_pause_playback. Name "spotify" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/spotify/framework/claude/ https://www.agent200.com/connectors/spotify/framework/chatgpt/ https://www.agent200.com/connectors/spotify/framework/claude-code/ https://www.agent200.com/connectors/spotify/framework/muse/ https://www.agent200.com/connectors/spotify/framework/grok-bot/ https://www.agent200.com/connectors/spotify/framework/openai-dots/ https://www.agent200.com/connectors/spotify/framework/claude-duet/ https://www.agent200.com/connectors/spotify/framework/hermes-agent/ https://www.agent200.com/connectors/spotify/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/spotify.md
Guides
Use Spotify with the AI you build on.
Step-by-step setup for Spotify with a specific model, assistant or agent framework.
-
Spotify + Claude
How to connect Spotify to Claude
-
Spotify + ChatGPT
How to connect Spotify to ChatGPT
-
Spotify + Claude Code
How to connect Spotify to Claude Code
-
Spotify + Muse
How to connect Spotify to Muse
-
Spotify + Grok Bot
How to connect Spotify to Grok Bot
-
Spotify + OpenAI Dots
How to connect Spotify to OpenAI Dots
-
Spotify + Claude Duet
How to connect Spotify to Claude Duet
-
Spotify + Hermes Agent
How to connect Spotify to Hermes Agent
-
Spotify + OpenClaw
How to connect Spotify to OpenClaw
FAQ
Spotify and Agent200, answered.
Who handles the Spotify OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Spotify.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Spotify connection, never another user's. It cannot reach anything the user or Spotify has not authorized.
Can I limit what my agent can do in Spotify?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.