Lineupify vs Azure DevOps (ADO)
A side-by-side look at the Lineupify and Azure DevOps (ADO) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declaredVerdict: choose Lineupify for developer tools work as a local process; choose Azure DevOps (ADO) 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.
AChoose Azure DevOps (ADO) when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 56/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,063 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 21 | Not listed |
| Full listing | View Lineupify | View Azure DevOps (ADO) |
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
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
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"
]
}
}
}
Azure DevOps (ADO)
{
"mcpServers": {
"azure-devops-ado": {
"command": "npx",
"args": [
"-y",
"@azure-devops/mcp"
]
}
}
}
Frequently asked questions
Lineupify is categorized under Developer Tools and uses a local stdio subprocess. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick Lineupify for developer tools work and Azure DevOps (ADO) 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. Azure DevOps (ADO) is listed as free. 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 azure-devops-ado 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. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,063 GitHub stars.