Spotify MCP integration for AI agents.
Connect AI agents to Spotify through 88 structured actions, including check saved albums, add item to playback queue, remove playlist items, and change playl…
- ACTION CONTRACTS
- 88
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Spotify integration exposes
The Spotify Agent App exposes 88 provider-backed actions for design and social work. Its current contract lets an authorized agent check saved albums using the spotify web api, add item to playback queue using the spotify web api, and remove playlist items using the spotify web api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Spotify account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Spotify capabilities.
Showing 12 of 88 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_saved_albumsREADCheck Saved Albums using the Spotify Web API.
INPUTS: albumIds / uris / description / public / collaborative
add_item_to_playback_queueWRITEAdd Item To Playback Queue using the Spotify Web API.
INPUTS: uris / description / public / collaborative / market
remove_playlist_itemsHIGH IMPACTRemove Playlist Items using the Spotify Web API.
INPUTS: playlistId / uris / items / description / public
change_playlist_detailsREVIEWChange Playlist Details using the Spotify Web API.
INPUTS: playlistId / uris / description / public / collaborative
add_items_to_playlistWRITEAdd Items To Playlist using the Spotify Web API.
INPUTS: playlistId / uris / description / public / collaborative
check_saved_audiobooksREADCheck Saved Audiobooks using the Spotify Web API.
INPUTS: audiobookIds / uris / description / public / collaborative
check_saved_episodesREADCheck Saved Episodes using the Spotify Web API.
INPUTS: episodeIds / uris / description / public / collaborative
check_saved_showsREADCheck Saved Shows using the Spotify Web API.
INPUTS: showIds / uris / description / public / collaborative
check_saved_tracksREADCheck Saved Tracks using the Spotify Web API.
INPUTS: trackIds / uris / description / public / collaborative
check_user_follows_artists_or_usersREADCheck User Follows Artists Or Users using the Spotify Web API.
INPUTS: ids / market / limit / offset / type
check_users_follow_playlistREADCheck Users Follow Playlist using the Spotify Web API.
INPUTS: playlistId / userIds / uris / description / public
create_playlistWRITECreate Playlist using the Spotify Web API.
INPUTS: userId / uris / name / description / public
INPUT CONTRACTS
Know what the action needs before it runs.
check_saved_albums
albumIdsREQUIRED- Spotify album IDs.
urisOPTIONAL- Spotify URIs in the order Spotify should use.
descriptionOPTIONAL- Playlist description.
publicOPTIONAL- Whether the playlist should be public.
collaborativeOPTIONAL- Whether the playlist should be collaborative.
add_item_to_playback_queue
urisOPTIONAL- Spotify URIs in the order Spotify should use.
descriptionOPTIONAL- Playlist description.
publicOPTIONAL- Whether the playlist should be public.
collaborativeOPTIONAL- Whether the playlist should be collaborative.
marketOPTIONAL- An ISO 3166-1 alpha-2 country code or from_token to apply market filtering.
remove_playlist_items
playlistIdREQUIRED- Spotify playlist ID.
urisOPTIONAL- Spotify URIs in the order Spotify should use.
itemsREQUIRED- Playlist item removal targets.
descriptionOPTIONAL- Playlist description.
publicOPTIONAL- Whether the playlist should be public.
change_playlist_details
playlistIdREQUIRED- Spotify playlist ID.
urisOPTIONAL- Spotify URIs in the order Spotify should use.
descriptionOPTIONAL- Playlist description.
publicOPTIONAL- Whether the playlist should be public.
collaborativeOPTIONAL- Whether the playlist should be collaborative.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Saved Albums
Check Saved Albums using the Spotify Web API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_saved_albumsControl Add Item To Playback Queue
Add Item To Playback Queue using the Spotify Web API. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_item_to_playback_queueVerify with Check Saved Audiobooks
Check Saved Audiobooks using the Spotify Web API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
check_saved_audiobooksSAFETY BOUNDARY
Operate Spotify with explicit limits
- Authorize Spotify with OAuth 2.0 and grant only the provider access required by the selected actions.
- 14 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `remove_playlist_items`, `remove_user_s_saved_audiobooks`, and `remove_user_s_saved_episodes` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `user-modify-playback-state`, `playlist-modify-public`, `playlist-modify-private`, and `user-library-read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Spotify task completed successfully.
CONNECTION MODEL
OAuth 2.0
Spotify uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 59
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 7
- REVIEW SIGNALS
- 15
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Spotify.