Agent workflow

MCP code review server for secure coding agents.

Radar's MCP security scanner turns local security, dependency, and code-health findings into tools an agent can query before proposing a risky change.

Summary

MCP code review server for secure coding agents

Radar's MCP security scanner turns local security, dependency, and code-health findings into tools an agent can query before proposing a risky change.

What is the Code Radar MCP server for?

The MCP server gives coding agents structured scanner findings, explanations, and scoped repair prompts so generated fixes start from deterministic evidence.

Does MCP replace a local scan?

No. MCP exposes scanner-backed context to the agent, but the repository still needs local scans and rescans to prove the fix actually removed the finding.

Which agents fit this workflow?

Use the MCP workflow with Codex, Claude, Cursor, or another MCP client when generated changes need concrete findings instead of broad review prompts.

When should MCP become a paid workflow?

Paid MCP use is justified when teams repeatedly need full scans, report exports, agent repair context, and CI gates around generated code.

AI-generated code security scanner for pre-PR review.

Use Radar as an AI code review tool to review AI-generated code from Codex, Claude, Cursor, Gemini, Qwen, or any agent workflow before the pull request exists.

Use case

Useful tools, not a chat transcript

Agents can ask for project summary, top findings, quality gate status, and repair prompts tied to the last scan, making Radar a practical MCP server for coding agents and a coding agent security tool.

  • scan_project_summary
  • explain_finding
  • run_quality_gate
  • radar://report

One local install

Install MCP config for common clients from the CLI.

radar mcp install all
radar mcp doctor

MCP workflow FAQ

Use these answers to separate scanner evidence, agent repair context, rescan proof, and the final merge decision.

What is the Code Radar MCP server for?

The MCP server gives coding agents structured scanner findings, explanations, and scoped repair prompts so generated fixes start from deterministic evidence.

Does MCP replace a local scan?

No. MCP exposes scanner-backed context to the agent, but the repository still needs local scans and rescans to prove the fix actually removed the finding.

Which agents fit this workflow?

Use the MCP workflow with Codex, Claude, Cursor, or another MCP client when generated changes need concrete findings instead of broad review prompts.

When should MCP become a paid workflow?

Paid MCP use is justified when teams repeatedly need full scans, report exports, agent repair context, and CI gates around generated code.