Repomix vs Spotify MCP
A side-by-side look at the Repomix and Spotify MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Repomix for developer tools work as a local process; choose Spotify MCP 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 Repomix when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pack_codebase, directory, compress.
Choose Spotify MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SPOTIFY_CLIENT_ID. - You want tools like
search, get_saved_tracks, get_saved_albums.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 64/100 · Good | 63/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 | SPOTIFY_CLIENT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 28,930 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 23 | 131 |
| Full listing | View Repomix | View Spotify MCP |
Tools & capabilities
Repomix tools 23
pack_codebasePackage a local code directory into a consolidated XML file for AI analysisdirectoryAbsolute path to the directory to packcompress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.attach_packed_outputAttach an existing Repomix packed output file for AI analysispathPath to a directory containing repomix-output.xml or direct path to a packed repository XML filepack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysisremoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.- +11 more on the listing page
Spotify MCP tools 131
searchSearch Spotify's catalog for tracks, artists, albums, playlists, shows, episodes, or audiobooks. Pass `types` as an array (e.g. `["artist"]`) to search a single kind — no track/album fallback noise. Decision guide: search (general, ≤10/type), search_deep (paginated fetch_all up to 50/type), search_fresh (tag:new last 2 weeks), search_by_isrc (exact ISRC), whats_new (personal radar from follows).get_saved_tracksGet tracks saved in the user's Liked Songs. Set fetch_all=true to retrieve the entire collection. Output is capped by max_results (default: SPOTIFY_MCP_MAX_ITEMS).get_saved_albumsGet albums saved in the user's library. Set fetch_all=true to retrieve the entire collection. Output is capped by max_results (default: SPOTIFY_MCP_MAX_ITEMS).get_saved_showsGet podcast shows saved in the user's library. Set fetch_all=true to retrieve the entire collection. Output is capped by max_results (default: SPOTIFY_MCP_MAX_ITEMS).get_saved_episodesGet podcast episodes saved in the user's library. Set fetch_all=true to retrieve the entire collection. Output is capped by max_results (default: SPOTIFY_MCP_MAX_ITEMS).save_to_libraryPreferred. Accepts the widest URI mix (track, album, episode, show, audiobook, user, playlist) in one request. Save one or more items to the user's library via Spotify's unified library endpoint. Max 40. PREVIEWS BY DEFAULT — pass dry_run=false to commit.remove_from_libraryPreferred. Accepts the widest URI mix (track, album, episode, show, audiobook, user, playlist) in one request. Remove one or more items from the user's library via Spotify's unified library endpoint. Max 40. PREVIEWS BY DEFAULT — pass dry_run=false to commit. Removals of 10+ items additionally require elicitation confirmation (or SPOTIFY_MCP_CONFIRM=never for automation).get_saved_countsLibrary size snapshot: counts for tracks/albums/shows/episodes/audiobooks/playlists via limit=1 reads — no item paging. The total covers library saves only: playlists are owned and followed collections, so their count is reported alongside the library rows and excluded from the total. A collection that could not be read (rate limited, gated, or erroring) is reported as unreadable with its reason and left out of the total — it is never reported as 0. One attempt per collection: a rate limit is surfaced, not retried. Quota: 6 GETs.search_saved_albumsSearch saved albums (client-side filter over bounded walk). Quota: GET /me/albums paged.search_saved_showsSearch saved podcast shows (bounded walk + client-side filter). Quota: GET /me/shows paged.search_saved_episodesSearch saved episodes (bounded walk + client-side filter). Quota: GET /me/episodes paged.search_saved_audiobooksSearch saved audiobooks (bounded walk + client-side filter). Quota: GET /me/audiobooks paged.- +119 more on 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.
Repomix
{
"mcpServers": {
"repomix": {
"command": "npx",
"args": [
"-y",
"repomix@latest"
]
}
}
}
Spotify MCP
{
"mcpServers": {
"spotify-mcp": {
"command": "npx",
"args": [
"-y",
"@novalux12/spotify-mcp@latest"
],
"env": {
"SPOTIFY_CLIENT_ID": "YOUR_SPOTIFY_CLIENT_ID_HERE"
}
}
}
}
Frequently asked questions
Repomix is categorized under Developer Tools and uses a local stdio subprocess. Spotify MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Repomix for developer tools work and Spotify MCP 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.
Repomix has no declared pricing — check the project's own site. Spotify MCP 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 repomix and spotify-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Repomix has a quality signal of 64/100 (Good) with 3 views, 0 installs and 28,930 GitHub stars. Spotify MCP has 63/100 (Good) with 2 views, 0 installs and 1 GitHub stars.