Chatpack MCP vs Tag Per Track
A side-by-side look at the Chatpack MCP 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 Chatpack MCP 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 Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
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 | 86/100 · Excellent | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | 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 | Verified | Community listing |
| GitHub stars | 224 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | 5 |
| Full listing | View Chatpack MCP | View Tag Per Track |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
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.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/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
Chatpack MCP 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 Chatpack MCP 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.
Chatpack MCP is listed as free. Auth: no auth required. 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 chatpack-mcp and tag-per-track as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 3 views, 0 installs and 224 GitHub stars. Tag Per Track has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.