Lineupify logo

Lineupify

Builds editable music playlist drafts from festival lineups, descriptions, songs, artists, and existing playlists.

Install Lineupify

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lineupify": {
      "command": "npx",
      "args": [
        "-y",
        "lineupify-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The lineupify MCP server turns festival lineups, genres, songs, artists, playlists, and blended sources into editable music playlist drafts. It runs locally and connects to Spotify or operates in Deezer mode, where results can be exported for use elsewhere. Drafts expose track, artist, and unresolved-item details before publishing, while playlist tools support analysis, comparison, merging, and expansion. Reach for it when an agent needs to prepare a festival playlist, refine a music brief, inspect playlist overlap, or transfer music between services.

Use cases

  • Build a playlist from a festival lineup
  • Create a playlist from a mood, genre, song, or artist
  • Compare and merge playlists for a shared listening session
  • Export a draft for import into another music service
  • Refresh music from followed or top artists

Key features

  • Festival lineup parsing with artist tiers, days, and stages
  • Editable drafts with track-level review and undo
  • Spotify playlist publishing and updating
  • Deezer-based draft creation and export
  • Playlist analysis, comparison, merging, and expansion
  • Markdown, CSV, M3U, link, and text exports

Tools21

What Lineupify lets your agent do. Expand a tool for its parameters.

Self-reported~807 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 18h ago via OSV.dev · lineupify-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads253Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed21Callable tools this server registers over MCP.

How Lineupify works

What lineupify MCP server does

The lineupify MCP server helps an MCP host turn music requests into drafts that can be inspected and changed before publication. Inputs can include raw festival poster text, a genre, a song, an artist, a chart, a country, a playlist, personal taste, or a blend of these sources. Lineup text can be normalized into artists with festival tiers, days, and stages while removing dates, stage labels, and ticket-related lines.

The result is a saved draft with track metadata, stable track identifiers, artist information, years, tempos, and unresolved items. An agent can review the draft, adjust it, and then publish it to Spotify or export it in a format suitable for another service.

How it works

Spotify mode uses the user’s own Spotify account and requires a Spotify Premium account plus a free developer app and Client ID. The server matches tracks by ISRC where available and selects popular songs for artists discovered from the request. Deezer mode does not require an account or key; it produces drafts with Deezer links rather than writing playlists.

Drafts may continue building in the background when a request is large. get_draft waits for progress and can resume an interrupted build. Saved drafts can be listed, deleted, exported, or published later. Published Spotify playlists can also be updated, subject to checks for changes made directly in Spotify.

Setup and configuration

The lineupify MCP server requires Node.js 20 or newer and is distributed as the lineupify-mcp npm package. A guided setup is available with npx -y lineupify-mcp init. The documented manual flow uses setup --client-id <id>, followed by auth, and then registers the server for a supported host.

The setup tool stores the Spotify Client ID in config.json. It can also store a Last.fm key or a fixed redirect port. The connect tool starts browser authentication and can save a Client ID during the same call. Use status first to inspect authentication, token expiry, defaults, draft activity, cache size, data location, and read-only state.

Tools and capabilities

The lineupify MCP server provides tools for:

  • Parsing lineup text and creating drafts from artists or multiple seed types.
  • Viewing, editing, searching, filtering, reordering, shuffling, and undoing draft changes.
  • Creating and updating Spotify playlists after review or explicit confirmation.
  • Reading, analyzing, comparing, merging, and expanding Spotify or Deezer playlists.
  • Comparing a draft with personal taste and refreshing recommendations from followed or top artists.
  • Exporting drafts as Markdown, CSV, M3U, links, or plain text, with optional local file saving.
  • Managing authentication, configuration, saved drafts, and Spotify disconnect or purge operations.

Limitations and notes

Deezer mode cannot create playlists because Deezer no longer issues write credentials; its exported links can be imported into other music services. Spotify access is limited to the account associated with the developer app and requires Premium. Spotify refresh tokens may require reconnection when they expire.

All processing runs on the local machine, with no Lineupify server or telemetry. Playlist reads are cached for 12 hours. Large drafts can take longer than the roughly 15-second response target and continue asynchronously. Deleting the local data directory requires an explicit confirmation and is refused if it contains files the application did not create.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Lineupify

lineupify is an MCP server that connects AI hosts to Spotify or Deezer for playlist creation and analysis. Its main tools parse lineups, create and edit drafts, search tracks, read and compare playlists, publish Spotify results, and export Deezer-compatible links or other playlist formats.

Install it with the `lineupify-mcp` npm package and run `npx -y lineupify-mcp init` for guided setup. The manual flow uses `setup --client-id <id>`, `auth`, and host registration. Node.js 20 or newer is required.

Yes, lineupify works with Cursor. The README names Cursor as a supported MCP host, and the guided setup can detect and register the server there. Restart the host after setup if required by the client.

No, Spotify mode requires a Spotify Premium account. It also needs a free Spotify developer app and its Client ID. Without Premium, use Deezer mode to create drafts and export links for transfer to another music service.

Use `export_draft` and choose Markdown, CSV, M3U, `links`, or `text`. The `links` and `text` formats are intended for transfer tools, and `save: true` writes the export below `~/.lineupify/exports/`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLineupify AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lineupify?style=directory)](https://allmcps.com/mcp/lineupify)
HTML Embed
<a href="https://allmcps.com/mcp/lineupify"><img src="https://allmcps.com/api/badge/lineupify?style=directory" alt="Lineupify on AllMCPs" /></a>