ContextBolt Radar in Codex watches up to 5 competitors and surfaces the changes that matter, straight from your terminal. Add one block to config.toml and competitive intelligence lives next to your code.
Codex is OpenAI’s command-line coding agent, and alongside Claude it is one of the agents ContextBolt is built around. It speaks the Model Context Protocol, so you can wire in ContextBolt Radar and keep watch on your competitors straight from your terminal workflow.
Codex has file access, so your watch list and every judged change mirror to a ./radar/ folder in your project as markdown. Your competitive history lives next to your code, searchable and version-controlled, instead of in a dashboard.
Competitor intel where you ship
When you are building, the question “did a competitor just change something that affects my plan?” is one you want answered without breaking flow. With Radar in Codex you ask it in the terminal and the judged answer comes back inline. No dashboard, no alert feed, no second tool.
Because these are MCP tools, Codex chains them. “Check rival.io, and if they changed pricing, draft a comparison page and list the talking points” is one prompt, not an afternoon of manual work, and the result is written to disk.
The config block
Add ContextBolt Radar to ~/.codex/config.toml:
[mcp_servers.contextbolt-radar]
url = "https://radar.contextbolt.app/mcp/YOUR_TOKEN"
Restart your Codex session so it reloads the config, then ask “what Radar tools do you have?” to confirm. Your URL contains a personal token, so keep config.toml out of public repos or pull the URL from an environment variable. Then name your competitors and the watching starts tonight.
How to connect ContextBolt Radar to Codex
-
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. Keep it private, like a password.
-
Add it to config.toml
Open ~/.codex/config.toml and add a server block: [mcp_servers.contextbolt-radar] on one line, then url = "https://radar.contextbolt.app/mcp/YOUR_TOKEN" on the next. Save the file.
-
Start a session and check it
Start a new Codex session so it reloads the config, then ask 'what Radar tools do you have?'. If it lists competitor, teardown, and digest tools, the server is connected.
-
Name your competitors
Say 'watch acme.com, rival.io and matter.com' with a line about what you sell. Radar runs an instant baseline and starts checking every night, briefing you each Monday once something moves.
Example prompts for ContextBolt Radar + Codex
Once connected, try asking Codex:
Adds each to your watch list (free) and stores your context, so every change is judged for your business rather than generically.
Reads all five surfaces plus search and returns an analyst read on day one, also setting the baseline for nightly diffs. Costs 5 credits.
Returns the judged changes with cosmetic noise removed, so you read moves that matter instead of raw diffs, straight from the terminal.
Codex pulls the receipts, then drafts the note in your voice and writes it to your project for review before you act.
What you can do with ContextBolt Radar in Codex
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 from the terminal
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 project
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