Use the Spotify CLI from KosmoKrator to call Spotify tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Spotify can be configured headlessly with `kosmokrator integrations:configure spotify`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure spotify --set access_token="$SPOTIFY_ACCESS_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor spotify --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Manual OAuth tokenoauth2_manual_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
SPOTIFY_ACCESS_TOKEN
Secret secret
yes
Access Token
url
SPOTIFY_URL
URL url
no
API URL
Call Spotify Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Spotify.
spotify.spotify_search
Read read
Search for tracks, artists, albums, or playlists on Spotify. Returns matching items with basic metadata. Use specific get tools for detailed information about a single item.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
spotify.spotify_search
Search for tracks, artists, albums, or playlists on Spotify. Returns matching items with basic metadata. Use specific get tools for detailed information about a single item.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.