QA Radar analyzes your codebase and produces a structured quality health report — combining git churn, test coverage, and test-to-source mapping into
QA Radar analyzes your codebase and produces a structured quality health report — combining git churn, test coverage, and test-to-source mapping into risk-scored modules. It works as an MCP server for AI coding agents (Claude Code. That is what the qaradar mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 8 tools. What each one is for:
qaradar_healthcheck — Full quality overview of a repositoryqaradar_risky_modules — What to test first; which files are riskiestqaradar_churn — Hotspot detection; where regressions tend to occurqaradar_coverage_gaps — Files with low coverage; where the blind spots areqaradar_untested_files — Source files with no corresponding test filesqaradar_pr_risk — Which changed files in this PR need attentionqaradar_should_run — After finishing work: should QA Radar re-analyze, and over the diff or the whole repo?Setup — Add to your Claude Code MCP config (~/.claude/mcp.json for user-level, or .mcp.json in the project root for project-level):qaradar on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Qaradar's toolset — qaradar_healthcheck, qaradar_risky_modules, qaradar_churn and 5 more — is a fair guide to whether it matches your workflow. It is maintained by muratkus; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| qaradar_healthcheck | Full quality overview of a repository |
| qaradar_risky_modules | What to test first; which files are riskiest |
| qaradar_churn | Hotspot detection; where regressions tend to occur |
| qaradar_coverage_gaps | Files with low coverage; where the blind spots are |
| qaradar_untested_files | Source files with no corresponding test files |
| qaradar_pr_risk | Which changed files in this PR need attention |
| qaradar_should_run | After finishing work: should QA Radar re-analyze, and over the diff or the whole repo? |
| Setup | Add to your Claude Code MCP config (~/.claude/mcp.json for user-level, or .mcp.json in the project root for project-level): |
{
"mcpServers": {
"qaradar": {
"command": "uvx",
"args": ["qaradar", "serve"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.