Magic MCP vs Qa Probe
A side-by-side look at the Magic MCP 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 Magic MCP 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.
Which MCP server should you choose?
Choose Magic MCP 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:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Choose Qa Probe 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
qa_probe_get_report, qa_probe_explain_failure, qa_probe_probe_endpoint.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Paid service | Free |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,997 | 2 |
| Directory activity | 16 views 1 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Magic MCP | View Qa Probe |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Qa Probe tools 8
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"
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.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Qa Probe
{
"mcpServers": {
"ls-siem-llp-qa-probe": {
"command": "npx",
"args": [
"-y",
"qa-probe"
]
}
}
}
Frequently asked questions
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. Qa Probe belongs to Developer Tools and uses a local stdio subprocess. Pick Magic MCP for developer tools work and Qa Probe 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.
Magic MCP is listed as a paid service. Auth: api key required. Qa Probe is listed as free. Auth: no auth required. 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 21st-dev-magic-mcp and ls-siem-llp-qa-probe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars. Qa Probe has 55/100 (Good) with 3 views, 0 installs and 2 GitHub stars.