A festival poster, a mood, a song you like or a friend’s playlist. Lineupify finds the artists, picks the songs and hands you a draft you can read and edit. Nothing is written to Spotify until you say publish.
Lineupify$ npx -y lineupify-mcp init
Where a playlist comes from
Your assistant turns what you said into artists and seeds. Lineupify resolves each artist, ranks their songs with Deezer’s public data and optionally Last.fm, then matches every track to Spotify by ISRC so you get the exact recording.
Names are sorted into headliner, sub and undercard, and each tier gets its own number of songs. Dates, stages and ticket lines are dropped.
Artists 9 (resolved 8 · unresolved 1) Tracks 27 · 1h42m · via isrc 25 / text 2 Tiers headliner 2×5 · sub 3×3 · undercard 4×2 Not found (1): DJ Fluffhead
Or a country, or an artist you like. Say how long it should be and whether it should stay clean; both are filters, not suggestions.
“Rainy Sunday jazz for cooking, about an hour, nothing explicit” Tracks 10 · 52:10 · clean only · private
Neighbours come from Last.fm and ListenBrainz co-listening data at the recording level, not from a genre guess.
“Songs like Ritviz – Udd Gaye, other artists only” seed similar_songs · pinned exact recordings
See what they share and why, then get one mix built from the artists several of you already like, plus their neighbours.
“What do our playlists share? Then make us a mix.” seed blend · 2 to 4 sources
The part that matters
An assistant with write access to your music library is only comfortable if you see the work first. Every build stops at a draft on your disk.
Every track with the artist it came from and how it was matched, plus the artists that were not found, by name.
Swap a song, drop an artist, reorder, undo. Ten revisions of history. Or export to CSV, M3U, Markdown or plain links.
Private by default. A read-only switch disables writes entirely, and Spotify’s API has no way to delete a playlist.
How it works
No black box in the middle. Each stage leaves something you can inspect, and a build that is interrupted picks up where it stopped.
Poster text, a mood, a genre, a song, a chart, a country, a playlist or your own taste become a list of artists with tiers.
Each artist is found on Deezer, then Last.fm if you added a key, then Spotify. Collaborations are split. Misses are recorded.
Songs are ranked, matched to Spotify by ISRC, deduplicated by recording, filtered by year, tempo or explicitness, then ordered.
The draft is checkpointed to disk after every artist, so a quota, a closed laptop or a dropped connection pauses it instead of losing it.
Worth knowing first
Most of these come from Spotify’s terms for new developer apps rather than from Lineupify. They are the reason it is built the way it is.
A new Spotify app serves at most five people and its owner must have Premium. Production access is granted only to registered businesses with 250,000 monthly users, so everyone brings their own free app. Add up to four other people under User Management in the dashboard.
Spotify removed artist top tracks, recommendations, popularity and audio features for new apps. Songs are ranked with Deezer’s public API and optionally Last.fm, then matched back to Spotify by ISRC. Very small or brand-new acts may be missing from Deezer and show up as unresolved.
Deezer stopped issuing API credentials to new developers in 2025, so Deezer drafts are exported rather than published. Reads, ranking, related artists and tempo stay keyless and unaffected.
Spotify refresh tokens die six months after you sign in; status warns you thirty days out. The daily request quota pauses a build rather than failing it, and the next get_draft resumes from the last checkpoint.
Documentation
Install it, point your assistant at a poster, and see what comes back. It costs nothing and it publishes nothing without you.
$ npx -y lineupify-mcp init