Playlist Zentrale lets Claude and other AI agents manage your own Spotify playlists. Every write is logged together with what was there before, and one call puts it back. A local dashboard shows what your listening actually looks like.
Source-available, free for noncommercial use. The hosted app has five seats and a waitlist.
Created Sunday Slow with 12 songs
21:14 claude-code · create_playlist · undoable
The dashboard
The real app, with an invented listener.
These are screens of the actual dashboard, served by bun run demo over a made-up library. Your own library looks like this after one login.
127.0.0.1:7173
Overview. Your number one artist, your day ones, pinned playlists and a printable receipt of your top 10.Analysis. Claude reads a digest of your library and writes what it hears. Every claim cites its evidence, and you see the exact text that is sent.Stats. When you hit like, how old songs are when you find them, how concentrated your taste is. Any period, from seven days to every year.Moods. Spotify closed audio features, so Claude tags your artists once. The map shows where your music sits and how your moods moved.Discover. Songs that fit a playlist, built from your own taste graph. Click a score for its arithmetic. After an add, Undo waits in the header.Live. Tour dates of the artists you actually play, ranked by how much they matter to you, with a calendar file for each.
Agents make mistakes. This one keeps the receipts.
Every change goes into an append-only log together with the state before it. undo_last restores that state, and refuses when you changed the playlist yourself in the meantime.
In Claude Code
you
Add my top five tracks of the last month to Run Club, skip what's already there.
tool
add_tracks · playlist "Run Club" · 5 tracks
Heavy DaydreamEmber Laneadded
Rolling SignalRotor Twinsadded
Orbit FeverNova Kestreladded
Copper EngineCopper Mothadded
Golden ParadeGolden Pylonalready there
agent
Added four, skipped one that was already in Run Club. Say "undo" and the list goes back to how it was.
Refused, shortened:NOT undone: playlist … ("Night Drive") changed after this write (31 items now, 30 right after the write). Restoring would throw that later edit away.
What a log line holds
The operation, the playlist, the full state before the write (tracks, name, description, public) and right after it, the client that made it and its process id. Undone-ness is derived from later undo lines; nothing is ever rewritten.
Security model
Built for a playlist name that tries to give orders.
An agent reads titles and descriptions written by strangers. The guardrails assume one of them will try a prompt injection.
01
Only your own playlists
Followed and collaborative playlists owned by someone else are refused before any call.
02
Logged before it returns
Every successful write is logged before the tool returns. If the log cannot be written, the tool says so loudly, with the previous state.
03
Undo never overwrites you
A drift check compares the live playlist with the state right after the write. A lockfile stops two sessions undoing the same change.
04
Destructive means explicit
Unfollowing needs confirm: true; building from a list is a dry run until apply: true.
05
Untrusted data, labelled
Every tool response starts with a banner that marks names and titles as data, never instructions.
06
Sandboxed cover uploads
Only .jpg files inside your picture folders, never hidden folders, with symlinks resolved first.
07
No secrets in output
Tokens and the client secret are redacted from every tool and CLI response. PKCE login, no secret needed.
08
A dashboard only you can reach
127.0.0.1 only, Host and Origin checks, a per-launch page token and a strict Content-Security-Policy.
What it reads
Everything Spotify still lets an app read, counted.
Spotify closed recommendations, audio features and related artists to new apps. The dashboard works with what is left: your playlists, likes, top lists and recent plays. Every number has a "How is this computed?" note.
11 tabs, from Overview to Discover
24 MCP tools, every write audited
0 network calls in the tests
# see it without an account
bun run demo
PLAYLIST ZENTRALE
your library, itemised
01Overviewtop 1
02AnalysisAI
03Top lists3 ranges
04History50 plays
05Libraryby month
06Stats6 KPIs
07Moods8 moods
08Linksnetwork
09Livenear you
10Playlistsfindings
11Discover+ undo
TOTAL0.00
free for noncommercial use
Get started
From clone to first tool call.
You need Bun 1.3 or newer and a Spotify developer app with the redirect URI http://127.0.0.1:3000/spotify/callback. The full walkthrough is in the README.
1Install and check
git clone https://github.com/noluyorAbi/playlist-zentrale.git
cd playlist-zentrale && bun install && bun run check
2Store your client id and log in
D=~/.config/playlist-zentrale; mkdir -p $D && chmod 700 $D
echo 'SPOTIFY_CLIENT_ID=your-client-id' > $D/secrets.env
chmod 600 $D/secrets.env && bun run login
3Connect your agent
claude mcp add --scope user playlist-zentrale -- \
"$(command -v bun)" "$PWD/src/mcp.ts"
bun run web # http://127.0.0.1:7173
bun run demo # invented data, no account
Hosted
Five seats, honestly.
Spotify runs every new app in Development Mode: at most five listeners, each added by hand. The hosted dashboard at zentrale.adatepe.dev is in that mode. If you have a seat, sign in there. If not, leave your email on its waitlist and you will hear once, when a seat opens.
Or run your own copy on Vercel: the same code, your own five seats, every stored file encrypted.
Locally: one folder, ~/.config/playlist-zentrale/, mode 0700. Delete it and everything is gone.
Leaves your machine, apart from the Spotify calls themselves, only when you press the button: names and counts to Claude for the analysis, artist names to Bandsintown for tour dates, song ISRCs to Deezer for tempo.
Hosted: your token and statistics, AES-256-GCM encrypted in a private store. "Delete my data" removes all of it.