# Use Optifeed Radar with Claude Code

Canonical HTML guide: https://radar.optifeed.com/claude-code/

Verified package: `optifeed-radar@0.1.0`

## Connect

Run this in the project where Claude Code should use Radar:

```bash
claude mcp add --transport stdio optifeed-radar -- \
  npx -y --package=optifeed-radar optifeed-mcp
```

Verify the server:

```bash
claude mcp get optifeed-radar
claude mcp list
```

Inside Claude Code, use `/mcp` to inspect connection status and tools. The default local scope associates the server with the current project.

## Start with the free audit

```text
Use Optifeed Radar to run a free AI-readiness audit on mybrand.com.
Explain the findings, but do not run any tool that spends API credit.
```

This maps to `audit_store`, which makes no AI calls and needs no provider key.

## Example paid prompt

```text
Check mybrand.com's AI visibility in quick mode.
Use only engines with configured keys and cap total spend at $0.20.
Show the evidence and limitations beneath the score.
```

## Provider keys

For paid tools, set one or more of `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GOOGLE_API_KEY`, and `PERPLEXITY_API_KEY` in the local environment or a project-local `.env` file. Do not paste key values into prompts or commit them.

Use `max_cost` whenever Claude starts a paid check unattended. The free `audit_store` and `get_snapshot_diff` tools do not call providers.

## Scope

Claude Code supports local, project, and user MCP scopes. Start with the default local scope. Promote the server to a broader scope only after the connection works in one project.

Official Claude Code MCP documentation: https://code.claude.com/docs/en/mcp
Repository: https://github.com/optifeed/optifeed-radar