This release includes breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+7 more
Summary
AI summaryThree new playlist management tools (get-playlist-tracks, delete-playlist, remove‑tracks-from-playlist) were added and the codebase updated for February 2026 Spotify Web API changes.
Full changelog
mcp-claude-spotify v0.4.0 - Playlist Management Tools & API Compatibility Updates
Release Date: Friday, March 20, 2026
Status: Production Ready
Summary
This release introduces v0.4.0 with three new playlist management tools, bringing full CRUD-like control over Spotify playlists. It also aligns the codebase with the February 2026 Spotify Web API changes and resolves a longstanding build synchronization issue from a previous release.
Major Features
New Playlist Management Tools
Three new MCP tools have been added to extend playlist control capabilities.
get-playlist-tracks
Retrieve tracks from any playlist with full pagination support.
- Parameters:
playlistId(required),limit(1-50, default 20),offset(default 0). - Endpoint: Uses the dedicated
GET /v1/playlists/{id}/tracksendpoint directly, returning a clean paging object. - Response: Includes track index, title, artists, album, duration, and pagination metadata.
- Commit:
3aa0efc,4d5f305
delete-playlist
Unfollow (remove) a playlist from the user's Spotify library.
- Note: The Spotify API does not support true playlist deletion; this tool unfollows the playlist, which removes it from the user's library.
- Commit:
3aa0efc
remove-tracks-from-playlist
Remove one or more specific tracks from a playlist by track ID.
- Parameters:
playlistId(required),trackIds(array of Spotify track IDs). - Commit:
3aa0efc
Spotify Web API Compatibility Updates (February 2026)
The codebase has been updated to align with breaking changes introduced in the Spotify Web API as of February 2026.
- Write Endpoint: Now uses
/playlists/{id}/itemsinstead of/playlists/{id}/tracksfor write operations. - DELETE Body Format: Requests now use
{ items }instead of{ tracks }as required by the updated API spec. - Track Data Reading: Track data is now read from
item.iteminstead ofitem.trackin playlist item responses. - Playlist Tracks Field: Playlist tracks are now read from
playlist.itemsinstead ofplaylist.tracks. - Commit:
3aa0efc,4d5f305
Bug Fixes
Build Synchronization
Rebuilt build/index.js to include all TypeScript source changes that were previously missing from the compiled output.
- Includes
getPlaylistItemTotal(),owner.display_namefallback, and other improvements from PR #26 that were not reflected in the prior build. - Commit:
3aa0efc
Migration Guide
For Users
No migration steps required. All three new tools are immediately available after updating.
For Developers
- Run
npm installoryarn installto pull in any updated dependencies. - If you maintain custom integrations that interact with playlist endpoints directly, update them to use
/itemsinstead of/tracksfor write operations and adjust request bodies accordingly.
Testing
- ✅
get-playlist-trackspagination and track data mapping - ✅
delete-playlistunfollow behavior - ✅
remove-tracks-from-playlisttrack removal by ID - ✅ February 2026 Spotify API endpoint and body format changes
- ✅ Build output synchronization with TypeScript source
Acknowledgments
We extend our gratitude to the following contributor for their valuable work in this release:
- @AnselmeSDR
Support & Feedback
For any issues, questions, or feedback, please visit our [GitHub repository](https://github.com/imprvhub/mcp-claude-spotify) and create a new issue.
Release Authorization
Approved by: @imprvhub
Architecture Review: Complete
Security Audit: Passed
Performance Testing: Validated
Full Changelog: https://github.com/imprvhub/mcp-claude-spotify/compare/0.3.0...0.4.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About imprvhub/mcp-claude-spotify
An integration that allows Claude Desktop to interact with Spotify using the Model Context Protocol (MCP).
Related context
Beta — feedback welcome: [email protected]