Spotify Bulk Actions Mcp
@khglynn
Bulk Spotify operations with confidence scoring - batch playlist creation, library exports, and human-in-the-loop review for uncertain matches. Perfect for importing podcast song lists.
Overview
What is Spotify Bulk Actions Mcp?
An MCP server for bulk Spotify operations: batch playlist creation, library exports, and large-scale library management. It features confidence scoring for batch searches, human-in-the-loop review, and built‑in rate limiting. Designed for importing song lists from podcast show notes.
How to use Spotify Bulk Actions Mcp?
Requires Python 3.10+, a Spotify Developer application, and one‑time authentication via setup_auth.py. After setup, connect the server to Claude Code by adding its configuration to ~/.claude/settings.local.json. The server exposes 18 tools covering library analysis, search, playlist management, and utilities.
Key features of Spotify Bulk Actions Mcp
- Confidence scoring for batch searches (HIGH / MEDIUM / LOW)
- Human‑in‑the‑loop review for uncertain matches
- Bulk operations handling 500+ songs with automatic rate limiting
- Library exports of saved tracks, followed artists, and summary
- Podcast‑playlist‑focused import pipeline from CSVs
- Automatic retry and caching to reduce repeat API calls
Use cases of Spotify Bulk Actions Mcp
- Create playlists from song lists (CSV) with automated matching
- Export and analyze your saved library (up to 10,000 songs)
- Find albums where you have 6+ saved songs (e.g., for vinyl shopping)
- Import large episode song lists from podcasts (500+ songs)
- Review and correct uncertain song matches via spreadsheet export
FAQ from Spotify Bulk Actions Mcp
What makes this different from other Spotify MCPs?
It provides confidence scoring, human‑in‑the‑loop uncertain‑match review, bulk operations for 500+ songs, library exports, and is built specifically for podcast playlists.
What are the prerequisites?
Python 3.10+, a Spotify account, and Spotify Developer credentials obtained from the Spotify Developer Dashboard.
How does authentication work?
One‑time browser login via setup_auth.py; the token is saved locally in .spotify_cache/ and auto‑refreshed when expired.
Does it handle Spotify’s rate limits?
Yes, with small delays between API calls, automatic retry on 429 errors, and caching to avoid redundant requests.
Where are credentials and data stored?
Credentials go in .env (gitignored). Auth tokens and cached data are stored in .spotify_cache/ (gitignored). No data is sent externally.
