Claude Code is Anthropic’s command-line interface for Claude. It runs in your terminal, reads your codebase, and can use MCP servers to connect to outside tools and data, including nightly competitor monitoring from ContextBolt Radar.
This is where Radar is at its best, because Claude Code has file access. Your watch list and every judged change mirror to a ./radar/ folder in your project as markdown, one file per competitor plus an index. Your competitive history stops living in a dashboard and becomes a searchable, git-trackable record next to your code.
Why competitor monitoring belongs in your terminal
If you are shipping the product, you are already in the terminal. Asking “what did my competitors do this week, and does any of it change my roadmap?” without switching tabs keeps you in flow. Claude Code calls the right tool, returns the judged changes inline, and writes them to disk so next week starts from what you already know.
Because these are MCP tools, Claude Code chains them. “Check rival.io, and if they changed pricing, draft a comparison page and a post for me to review” is one prompt, not an afternoon of manual checking and writing.
Config file alternative
If you prefer editing config directly, add ContextBolt Radar to .mcp.json in your project root:
{
"mcpServers": {
"contextbolt-radar": {
"type": "http",
"url": "https://radar.contextbolt.app/mcp/YOUR_TOKEN"
}
}
}Two things worth flagging. Claude Code requires "type": "http" for remote servers, so leaving it out makes the connection fail silently. And your URL holds a personal token, so if you commit .mcp.json to a public repo, swap the token for an env var and set it locally. Once claude mcp list shows it connected, name your competitors and the watching starts tonight.
How to connect ContextBolt Radar to Claude Code
-
Subscribe and get your MCP URL
Subscribe to ContextBolt Radar ($39/month, up to 5 competitors). Your private MCP URL arrives by email and looks like https://radar.contextbolt.app/mcp/YOUR_TOKEN. Treat it like a password and keep it out of public repos.
-
Add it with one command
In your terminal run: claude mcp add --transport http contextbolt-radar https://radar.contextbolt.app/mcp/YOUR_TOKEN. Add --scope user before the name to make it available in every project, or leave it off to scope it to the current repo.
-
Confirm the connection
Run claude mcp list and you should see contextbolt-radar with a connected status. Then start a session and ask 'what Radar tools do you have?'. If it lists competitor, teardown, and digest tools, you are live.
-
Name your competitors
Say 'watch acme.com, rival.io and matter.com, and here is what I sell' with a line about your product. Radar runs an instant baseline and starts checking every night. The first Monday briefing lands once it has changes to report.
Example prompts for ContextBolt Radar + Claude Code
Once connected, try asking Claude Code:
Adds each domain to your watch list (free) and stores your context, so every future change is judged for your business, not generically.
Calls radar_teardown to read all five surfaces plus their search footprint and return an analyst read on day one. Costs 5 credits.
Pulls the judged changes and briefs you, with the cosmetic noise already filtered out, so you read moves that matter, not diffs.
Claude Code pulls the receipts with radar_history, then drafts a comparison page and a short post in your voice, saved to your repo for review before anything ships.
What you can do with ContextBolt Radar in Claude Code
Watch up to 5 competitors across pricing, homepage, changelog, sitemap, and search
Get every change judged for significance, so cosmetic noise never reaches you
Ask what changed this week in plain English, no dashboard
Get an instant teardown of any competitor on day one
See a rival's trajectory, like a second price rise since January
Have the counter-move drafted in your voice and saved to your repo
Read a Monday briefing of real moves, each with a counter-move and receipts
Save your radar to a ./radar/ folder as markdown you can grep and commit