MCP Clients

Radar exposes the same four tools through MCP:

• ask
• search
• summarize
• write

The MCP server runs over stdio:

radar-mcp

Cursor

Add Radar to .cursor/mcp.json:

{
  "mcpServers": {
    "radar": {
      "command": "radar-mcp"
    }
  }
}

Then copy the routing rule into .cursor/rules/radar-delegation.mdc. Installing Radar does not do this automatically.

Claude Code

Add Radar to your Claude MCP config:

{
  "mcpServers": {
    "radar": {
      "command": "radar-mcp"
    }
  }
}

Then add the routing guidance from AGENTS.md to your project CLAUDE.md.

Codex

Add Radar to ~/.codex/config.toml:

[mcp_servers.radar]
command = "radar-mcp"

Then add the routing guidance from AGENTS.md to your project instructions.

Routing Guidance

Radar's MCP descriptions are the primary routing signal. The included AGENTS.md, CLAUDE.md, and Cursor rule are optional templates for projects that want a stronger first-turn nudge:

Before broad reading, searching, summarizing, or drafting, check whether one Radar call can reduce the host context you are about to spend.

Keep local instructions short. Radar works best when the client sees clear triggers, not a long policy document.

Environment Variables

Most MCP clients inherit environment variables from the shell or support an env file. Ensure the MCP server receives at least:

RADAR_API_KEY=sk-...

See Configuration for provider and limit options.