Claude Task Master vs Tag Per Track
A side-by-side look at the Claude Task Master 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 Claude Task Master 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 Claude Task Master when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
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 | 61/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | ANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS | 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 | 28,255 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Claude Task Master | View Tag Per Track |
Tools & capabilities
Claude Task Master tools
No tool names declared yet. Check the project README from 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.
Claude Task Master
{
"mcpServers": {
"eyaltoledano-claude-task-master": {
"command": "npx",
"args": [
"-y",
"task-master-ai"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE",
"TASK_MASTER_TOOLS": "YOUR_TASK_MASTER_TOOLS_HERE"
}
}
}
}
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
Claude Task Master 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 Claude Task Master 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.
Claude Task Master is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 eyaltoledano-claude-task-master and tag-per-track as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Claude Task Master has a quality signal of 61/100 (Good) with 9 views, 0 installs and 28,255 GitHub stars. Tag Per Track has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.