Integration

ContextBolt Radar in Cursor (2026 Setup Guide)

Beginner 2 minutes setup By David Hamilton

Cursor is the AI-first code editor a lot of builders now live in. It speaks the Model Context Protocol, so you can plug in ContextBolt Radar and keep an eye on your competitors from the same window where you ship.

Like Claude Code, Cursor has file access, so your watch list and every judged change mirror to a ./radar/ folder in your workspace as markdown. Your competitive history lives next to your code, version-controlled and searchable, instead of in a dashboard you forget to open.

Competitor intel without leaving the editor

When you are heads-down building, the last thing you want is another tab to babysit. With Radar in Cursor you ask “what did my competitors do this week?” and the judged answer comes back in the chat pane. No dashboard, no alert feed, no context switch.

Because these are MCP tools, Cursor chains them. “Check rival.io, and if they shipped anything that overlaps our roadmap, summarize it and draft a positioning note” is one prompt that calls several tools and writes the result to disk.

Keeping the config clean

Add the server to your global ~/.cursor/mcp.json so it follows you across projects, or to a project-level .cursor/mcp.json if you only want it in one workspace:

{
  "mcpServers": {
    "contextbolt-radar": {
      "url": "https://radar.contextbolt.app/mcp/YOUR_TOKEN"
    }
  }
}

Your URL holds a personal token, so prefer the global config over a committed project file, or pull the URL from an environment variable. Once it shows a green dot in Settings, MCP, name your competitors and the watching starts tonight.

How to connect ContextBolt Radar to Cursor

  1. 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.

  2. Add it to your mcp.json

    Open Cursor Settings, then MCP, then Add new MCP server, or edit ~/.cursor/mcp.json directly. Under mcpServers add: "contextbolt-radar": { "url": "https://radar.contextbolt.app/mcp/YOUR_TOKEN" }. Save the file.

  3. Enable and check it

    Back in Settings, MCP, make sure contextbolt-radar shows a green dot and its tools are toggled on. Then open the chat pane and ask 'what Radar tools do you have?'. If it lists competitor, teardown, and digest tools, you are live.

  4. 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 + Cursor

Once connected, try asking Cursor:

Watch my competitors: acme.com, rival.io, matter.com. I sell a $20/mo invoicing app for freelancers.

Adds each to your watch list (free) and stores your context, so every change is judged for your business rather than generically.

Give me a teardown of rival.io.

Reads all five surfaces plus search and returns an analyst read on day one, also setting the baseline for future nightly diffs. Costs 5 credits.

What did my competitors do this week?

Returns the judged changes with the cosmetic noise removed, so you read moves that matter instead of raw diffs.

rival.io raised their Pro price. Draft my response.

Cursor pulls the receipts, then drafts a comparison page and a post in your voice, written into your workspace for review before anything ships.

What you can do with ContextBolt Radar in Cursor

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 while you build

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 workspace

Read a Monday briefing of real moves, each with a counter-move and receipts

Save your radar to ./radar/ in your workspace as markdown you can grep and commit

ContextBolt Radar + Cursor: FAQs

Where exactly does the config go? +
Cursor reads MCP servers from ~/.cursor/mcp.json for global use, or .cursor/mcp.json inside a project for that workspace only. Add contextbolt-radar under the mcpServers object with your URL, then enable it in Settings, MCP.
The server shows up but the tools are greyed out. Why? +
Cursor lists a server before you enable its tools. Open Settings, MCP, find contextbolt-radar, and toggle it on. If it still will not connect, re-check that the URL is pasted in full with no trailing space.
What is the ./radar/ folder? +
Every competitor you watch gets a markdown file in a ./radar/ folder in your workspace, plus an INDEX, mirrored from your account. You can grep it, commit it, or open it in Obsidian. The files are free and do not count against your credits.
How many credits does monitoring cost? +
The nightly and weekly watching is free and never touches your credits. You get 300 credits a month for on-demand work: a teardown is 5 credits, an on-demand check is 1 per competitor. Adding competitors, the digest, history, and counter-moves are all free.
Can I keep my token out of a shared repo? +
Yes. Put the server in your global ~/.cursor/mcp.json rather than a committed project file, or use an environment variable for the URL. Your MCP URL contains a personal token, so treat it like a password.