A side-by-side look at the Claude Task Master and Qa Probe 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 Qa Probe for developer tools as a local process. You can also run both side by side in one mcpServers block.
ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.qa_probe_get_report, qa_probe_explain_failure, qa_probe_probe_endpoint.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | ANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 28,227 | 2 |
| Directory activity | 9 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Claude Task Master | View Qa Probe |
No tool names declared yet. Check the project README from the listing page.
qa_probe_get_report"Show me all broken routes and their scores"qa_probe_explain_failure"Why is /reports showing no data?"qa_probe_probe_endpoint"Is GET /users returning data right now?"qa_probe_get_graph"Which backend routes does /dashboard call?"qa_probe_get_blast_radius"What pages break if the users endpoint goes down?"qa_probe_suggest_fix"What should I do about feature_flag_disabled?"qa_probe_run_analysis"Run a full QA check and give me the summary"qa_probe_label"Mark this finding as expected / a real bug"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.
{
"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"
}
}
}
}
{
"mcpServers": {
"ls-siem-llp-qa-probe": {
"command": "npx",
"args": [
"-y",
"qa-probe"
]
}
}
}