# 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.

- Page: https://www.agent200.com/connectors/spotify/
- Category: Files and knowledge
- Authentication: Managed OAuth
- Identifier in code: `spotify`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## Spotify tools

- **Search** (`spotify_search`, read): Search for tracks, albums, artists, playlists and shows.
- **List playlists** (`spotify_list_playlists`, read): List the user's playlists.
- **Create a playlist** (`spotify_create_playlist`, write): Create a new playlist.
- **Add tracks to a playlist** (`spotify_add_tracks`, write): Add tracks to a playlist.
- **Get the playing track** (`spotify_get_playing`, read): See what is playing on the user's account.
- **List recently played** (`spotify_list_recently_played`, read): List the tracks the user played recently.
- **Start playback** (`spotify_start_playback`, write): Start or resume playback on an active device.
- **Pause playback** (`spotify_pause_playback`, write): Pause playback on an active device.

## Limits you can set

**Turn single tools on or off.** Let the agent search and control playback, and switch off `spotify_create_playlist` so 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "Make a playlist of upbeat songs for my run"
- "What song is this"
- "Add this track to my Focus playlist"
- "Pause the music"

## Guides: Spotify with your AI framework

- [Spotify + Claude](https://www.agent200.com/connectors/spotify/framework/claude.md): Connect Spotify to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Spotify + ChatGPT](https://www.agent200.com/connectors/spotify/framework/chatgpt.md): Give ChatGPT access to Spotify through Agent200: managed OAuth, ready-made tools and one API key.
- [Spotify + Claude Code](https://www.agent200.com/connectors/spotify/framework/claude-code.md): Have Claude Code build a Spotify agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Spotify + Muse](https://www.agent200.com/connectors/spotify/framework/muse.md): Connect Spotify to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Spotify + Grok Bot](https://www.agent200.com/connectors/spotify/framework/grok-bot.md): Connect Spotify to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Spotify + OpenAI Dots](https://www.agent200.com/connectors/spotify/framework/openai-dots.md): Give OpenAI Dots access to Spotify through Agent200: managed OAuth, ready-made tools and one API key.
- [Spotify + Claude Duet](https://www.agent200.com/connectors/spotify/framework/claude-duet.md): Connect Spotify to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Spotify + Hermes Agent](https://www.agent200.com/connectors/spotify/framework/hermes-agent.md): Connect Spotify to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Spotify + OpenClaw](https://www.agent200.com/connectors/spotify/framework/openclaw.md): Connect Spotify to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [Google Drive](https://www.agent200.com/connectors/google-drive.md): Find, read and organize the files in each user's Drive.
- [OneDrive](https://www.agent200.com/connectors/onedrive.md): Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.
- [Dropbox](https://www.agent200.com/connectors/dropbox.md): Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.
- [Notion](https://www.agent200.com/connectors/notion.md): Search, read and write Notion pages and databases on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
