Lineupify vs Tag Per Track
A side-by-side look at the Lineupify and Tag Per Track MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lineupify for developer tools work as a local process; choose Tag Per Track for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lineupify when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
status, setup, connect.
Choose Tag Per Track when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TAG_PER_TRACK_API_KEY, WALLET_PRIVATE_KEY, MAX_SPENDING_USDC, PLATFORM_WALLET, TAG_PER_TRACK_NO_PERSIST, API_URL, API_BASE_URL. - You want tools like
analyze_audio, analyze_audio_with_lyrics, triage_demo_folder.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 56/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TAG_PER_TRACK_API_KEYWALLET_PRIVATE_KEYMAX_SPENDING_USDCPLATFORM_WALLETTAG_PER_TRACK_NO_PERSISTAPI_URLAPI_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 21 | 5 |
| Full listing | View Lineupify | View Tag Per Track |
Tools & capabilities
Lineupify tools 21
statusCall first. Shows connection state (and as whom), setup steps if needed, token expiry, defaults, drafts in progress, cache size, data directory and any read-only mode.setupSaves the Spotify Client ID (and optionally a Last.fm key or a fixed redirect port) to `config.json`.connectStarts the Spotify login: opens the browser and returns the URL immediately. Pass `clientId` to save the app's Client ID in the same call. Refused while a draft is building.disconnectForgets the Spotify login; with `purge: true` (plus `confirm: true`, after you agreed in the conversation) deletes the whole `~/.lineupify` folder. Refuses if that folder holds files Lineupify did not create. Tells you where to remove the app's access on Spotify's side.parse_lineupTurns raw poster text into a clean artist list with tiers, days and stages; drops dates, stage names and "tickets" lines.create_draftBuilds a draft from artists and/or seeds (genre, similar artist, chart, country, playlist, your taste, a blend). Returns within ~15 s; larger builds continue in the background.get_draftShows a draft: `summary` (default), `tracks` (paged, with stable ids, year and tempo), `artists`, or `unresolved`. Waits for progress while building. Also resumes an interrupted build.edit_draftApplies one or more edits atomically. Ops: `remove_tracks`, `add_track`, `exclude_artist`, `set_artist_track_count`, `set_artist_source`, `move`, `shuffle`, `reorder`, `set_meta`, `filter`, `undo`.search_tracksSearches Spotify, or Deezer for a Deezer draft, for a track to add manually; supports `track:` / `artist:` filters.create_playlistPublishes a ready draft as a new playlist and returns its URL. Requires the draft to have been shown to the user or `confirm: true`.update_playlistReplaces the tracks and details of the playlist a draft was published to. Refuses if the playlist changed inside Spotify unless `force: true`.compare_tasteMarks each artist in a draft as known (in your top or followed artists) or new to you.- +9 more on the listing page
Tag Per Track tools 5
analyze_audioAnalyzes a music track or audio file to extract musical metadata (BPM, genre, mood, key, instruments), AI music detection verdict (HUMAN vs AI_GENERATED Suno/Udio neural vocoder risk with confidence index in 'ai_detection'), explainable A&R scoring v2 in 'arEvaluation' (discovery / signing / beatmaker profiles, AI gate, vocal vs instrumental), and optionally vocal lyrics. Supports local audio files via 'filePath' (read in binary and uploaded) or remote URLs via 'fileUrl'. Cost: 1 studio credit per track, 2 studio credits with lyrics, debited from the prepaid Studio balance. Always state costs in studio credits.analyze_audio_with_lyricsAnalyzes an audio track to extract complete musical metadata, AI-generated music detection verdict (HUMAN vs AI_GENERATED Suno/Udio), AND transcribe full vocal lyrics using AI. Supports local audio files via 'filePath' (read in binary and uploaded) or remote URLs via 'fileUrl'. Costs 2 studio credits per track. (Alias for analyze_audio with extractLyrics: true).triage_demo_folderA&R demo inbox triage in ONE call: scans a local folder of demo submissions (.mp3, .wav, .flac, .m4a, .aiff...), analyzes every track, reads the artist/title from audio tags or 'Artist - Title' file names, fetches Spotify traction per artist, applies A&R scoring v2 and returns a COMPACT ranked report (score, priority, bucket, BPM/key/genre, AI-origin flag, monthly listeners, key reason codes, guarded lyrics excerpt). Buckets: 'priority' (listen first), 'listen', 'pass', 'ai_flagged' (confirmed or suspected AI-generated), 'error' (unreadable or rejected file), 'not_analyzed' (the triage stopped early because studio credits ran out or the API key was rejected: see 'halted'). Prefer this tool over analyze_audio_batch whenever the user wants to sort, rank or screen a folder of demos. Cost: 1 studio credit per track, 2 studio credits with lyrics, debited from the prepaid Studio balance. Always state costs in studio credits. Use dryRun to list files and the estimated cost (estimatedCost.label) without charging.analyze_audio_batchAnalyzes multiple music tracks or audio files in parallel (batch processing). Vastly reduces total execution time compared to sequential processing. Accepts a list of local file paths ('filePaths') or remote URLs ('fileUrls'), or a structured array of 'tracks'. Cost: 1 studio credit per track, 2 studio credits with lyrics, debited from the prepaid Studio balance. Always state costs in studio credits.lookup_artist_statsRetrieves streaming traction and commercial metrics for an artist (Spotify monthly listeners, followers, popularity score) for A&R qualification.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lineupify
{
"mcpServers": {
"lineupify": {
"command": "npx",
"args": [
"-y",
"lineupify-mcp"
]
}
}
}
Tag Per Track
{
"mcpServers": {
"tag-per-track": {
"command": "npx",
"args": [
"-y",
"tag-per-track-mcp@latest"
],
"env": {
"TAG_PER_TRACK_API_KEY": "YOUR_TAG_PER_TRACK_API_KEY_HERE",
"WALLET_PRIVATE_KEY": "YOUR_WALLET_PRIVATE_KEY_HERE",
"MAX_SPENDING_USDC": "YOUR_MAX_SPENDING_USDC_HERE",
"PLATFORM_WALLET": "YOUR_PLATFORM_WALLET_HERE",
"TAG_PER_TRACK_NO_PERSIST": "YOUR_TAG_PER_TRACK_NO_PERSIST_HERE",
"API_URL": "YOUR_API_URL_HERE",
"API_BASE_URL": "YOUR_API_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Lineupify is categorized under Developer Tools and uses a local stdio subprocess. Tag Per Track belongs to Developer Tools and uses a local stdio subprocess. Pick Lineupify for developer tools work and Tag Per Track for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Lineupify has no declared pricing — check the project's own site. Tag Per Track has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lineupify and tag-per-track as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lineupify has a quality signal of 56/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Tag Per Track has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.