Connect your AI Agents to Spotify in minutes

What is a Spotify MCP?

It's an MCP server that connects your agents to Spotify's music platform via tools. Your agents can invoke these tools to search for music, control playback, manage playlists, access listening history, and more.

Spotify doesn't offer an official MCP server, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Spotify MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Mood-based playlist generation: When a user describes what they want to listen to in a chat interface, an agent searches Spotify for matching tracks, creates a new playlist, adds them to it, and starts playback on the user's active device

• Automatic workout playlist updates: When a user logs a workout in a fitness app, an agent checks the activity type, searches Spotify for tracks matching the right energy level, and adds new songs to the user's workout playlist to keep it fresh

• Weekly listening recap: On a Friday schedule, an agent pulls the user's top tracks and recently played history from Spotify, formats them into a digest, and sends the summary by Slack message or email

• Context-aware focus music: When a deep work session starts in a calendar or productivity tool, an agent begins a low-distraction playlist on the user's Spotify device and pauses playback automatically when the session ends

What are popular tools for Spotify's MCP server?

Here are some of the most commonly used tools:

• search: searches Spotify for tracks, artists, albums, playlists, or podcasts matching a text query. Use this when an agent needs to find specific music content before adding it to a queue, playlist, or playback session

• start_playback: begins or resumes playback on a specified device, optionally targeting a track, album, or playlist URI. Call this when an agent needs to trigger music in response to a user action or a scheduled workflow event

• create_playlist: creates a new Spotify playlist for the current user with a name, description, and visibility setting. Use this when an agent is assembling a curated set of tracks and needs a destination to collect them

• add_playlist_items: adds one or more tracks to an existing Spotify playlist by URI. Good for agents that build playlists incrementally from search results, user preferences, or external recommendation data

• get_currently_playing: returns the track currently playing on the user's Spotify account, including track name, artist, and playback state. Helpful when an agent needs to check what's active before making a queue management or logging decision

• get_user_top_items: returns the user's top tracks or artists over a short, medium, or long time range. Use this when an agent needs to personalize recommendations or generate a listening summary based on real listening behavior

What makes Merge Agent Handler's Spotify MCP server better than alternative Spotify MCP servers?

Spotify doesn't have an official MCP server, so if you're choosing between a community implementation and a managed platform, here's what differentiates Merge Agent Handler:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Spotify, this means you can prevent listening history, playlist contents, and user account details from being surfaced to agents that don't specifically need them

• Managed authentication and credentials: Merge stores and manages your Spotify OAuth credentials on your behalf. You never embed tokens in agent configuration or deal with re-authorization when they expire after the standard one-hour window

• Real-time observability and audit trail: Every tool call against Spotify is logged with timestamp, tool name, parameters, and response data. Teams building music-integrated products can audit exactly what an agent played, searched, or modified without any custom instrumentation

• Tool Packs and controlled access: Tool Packs let you bundle specific Spotify tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Spotify MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Spotify connector. Match tools to your use case. For example, use search and get_user_top_items for discovery and reporting, and use tools like start_playback, create_playlist, and add_playlist_items to control playback or manage music libraries.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Spotify by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Spotify tools are now accessible through that endpoint.