spotify-mcp: Skill for Claude Code

Spotify API watch

Spotify ships breaking changes to the Web API with little notice and no RSS feed. This skill answers two questions: what did Spotify change, and does our server still work. Do both — a clean changelog does not mean nothing broke, because the regime flip described below happens silently.

1. Changelog sweep

uv run scripts/spotify_api_watch.py

Exit 1 means there are unreviewed entries. Spotify publishes no feed and no changelog index, so this probes the predictable per-month URLs (.../references/changes/<month>-<year>) and diffs against scripts/spotify-api-seen.json.

For each NEW URL, fetch it and classify every item as:

• Breaks us — an endpoint spotipy calls, a field one of the Pydantic models in src/spotify_mcp/fastmcp_server.py requires, or a path in the fallback layer at the bottom of src/spotify_mcp/spotify_api.py.
• Unlocks something — new capability worth a tool or a scope.
• Irrelevant — dashboard/quota/billing with no code impact.

Then re-run with --accept to record them as reviewed, and commit the updated JSON. Only accept after you have actually read the entries.

2. Live conformance probe

The changelog tells you what Spotify announced; this tells you what our app actually gets. Requires the server connected as an MCP client — ask the user to reconnect if the tools are absent.

Run these and compare against the expectations:

Call	Full/legacy regime	Restricted regime
get_me	returns email, country, product	id only
get_artist on any artist	has followers, popularity	both absent
search_music with limit=20	can return >10	capped at 10
save_tracks on one id	succeeds via legacy /me/tracks	succeeds via /me/library

If the probe shows a flip to restricted, expect these to matter:

• search_music max drops 50 → 10 (our schema still advertises 50).
• Artist followers/popularity and user email/country/product vanish. Those fields are all optional on the Pydantic models, so they degrade rather than throw — keep them that way.
• Playlist and library writes move to /items and /me/library. with_fallback in spotify_api.py handles this, but it caches per process, so the first call after a flip may fail before it settles. Watch for the "resolved to the legacy regime" log line to see which way it went.