In-depth architectural comparison of the Lineupify and Payram Helper MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Lineupify
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Payram Helper MCP Server
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Lineupify if you need specialized Developer Tools tools running via a local process. Choose Payram Helper MCP Server if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
L
Choose Lineupify when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Call 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.
setup
Saves the Spotify Client ID (and optionally a Last.fm key or a fixed redirect port) to `config.json`.
connect
Starts 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.
disconnect
Forgets 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_lineup
Turns raw poster text into a clean artist list with tiers, days and stages; drops dates, stage names and "tickets" lines.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Lineupify is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Payram Helper MCP Server belongs to Developer Tools using local stdio subprocess. Select Lineupify when you need capabilities focused on developer tools and Payram Helper MCP Server when you require tools for developer tools.
Builds 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_draft
Shows 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_draft
Applies 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_tracks
Searches Spotify, or Deezer for a Deezer draft, for a track to add manually; supports `track:` / `artist:` filters.
create_playlist
Publishes 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_playlist
Replaces the tracks and details of the playlist a draft was published to. Refuses if the playlist changed inside Spotify unless `force: true`.
compare_taste
Marks each artist in a draft as known (in your top or followed artists) or new to you.
+9 more tools listed on main page
Payram Helper MCP Server Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.