Spotify
Search Spotify's catalog and manage playlists, profile and playback state.
About
Spotify ships in the w6w first-party pack. It declares 9 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.spotify- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity
Overview
Spotify searches the catalog and manages playlists, profile and playback state through Spotify’s own Web API. Tracks, albums and artists can be looked up directly, and search runs across the whole catalog — all without any special scope, since catalog reads work with any valid user token. A user’s own profile, including their subscription tier, and what’s currently playing can also be read.
Playlists can be listed — including private ones — created, and have tracks added to them, using Spotify’s current playlist-creation endpoint rather than the older, removed one. Every id or URI parameter accepts either a bare Spotify id or a full spotify: URI, so a value copied straight from a link or a share doesn’t need to be parsed first.
Playback control — play, pause, skip, queue, volume — is left out, since every one of those needs an active, connected Spotify device and fails outright the moment nothing is playing, which fits poorly with an unattended workflow step. Liked tracks, followed artists and Spotify’s deprecated audio-analysis endpoints are left out for the same reason: either not yet requested, or already retired by Spotify itself.
Build with Spotify
Three routes to the same 9 actions. The Workflow tab is generated from Spotify's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Currently Playing
player-get-currently-playing Get the track currently playing on the connected account, if any.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Spotify's real ids.
{
"manifestVersion": "2",
"name": "spotify-example",
"steps": [
{
"id": "album-get",
"uses": {
"app": "io.w6w.spotify",
"action": "album-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Album
readalbum-get -
Get Artist
readartist-get -
Get Currently Playing
readplayer-get-currently-playing -
Add Tracks to Playlist
performplaylist-add-tracks -
Create Playlist
performplaylist-create
+4 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Spotify, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Spotify. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "playlist-create",
payload: {
name: "<value>",
// description: "<value>",
// public: "<value>",
// collaborative: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action playlist-create --payload '{"name":"<value>"}'Give an AI agent Spotify — without giving it Spotify's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.spotify#album-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Spotify connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Spotify's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Spotify itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Spotify declares its own checks, so its health is a property of the app rather than something the host guesses at.
Spotify platform status
Atlassian Statuspage rollup for spotify.statuspage.io, with per-component detail. Unauthenticated and unsigned.