← All integrations

Radar MCP server

16 operations0 webhooks

Location infrastructure with Radar - geocode addresses and coordinates, search places and geofences, read tracked users, geofences and trips, upsert a geofence, submit location updates and log conversions.

Use Radar in Claude, ChatGPT, Cursor or another MCP client

Connect Radar once in Corsair, then add one MCP address to your agent.

Connect Radar
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Radar with your agent

Connect Radar, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Radar on my account, then run one read-only example and show me the result.

Runs once, when you ask

Radar tools and triggers

Tools are what your agent can do in Radar through Corsair's MCP server. Triggers are the Radar events a routine can start from.

Geofences

  • DeleteDestructive

    Delete a geofence permanently; the API keeps no copy

    geofences.delete

  • GetRead-only

    Fetch one geofence with its geometry, radius and metadata

    geofences.get

  • ListRead-only

    List geofences with tag and external-id filters, paging by update time

    geofences.list

  • UpsertWrite

    Create or replace a geofence by tag and external id, or by Radar id: a circle, a polygon or an isochrone

    geofences.upsert

Trips

  • CreateWrite

    Create a trip for a user with its destination geofence, travel mode and approaching threshold

    trips.create

  • GetRead-only

    Fetch one trip with its status, destination and live ETA

    trips.get

  • ListRead-only

    List trips by status, user, destination or time window, optionally with their location trace

    trips.list

  • UpdateWrite

    Update a trip: its status, mode, destination or approaching threshold

    trips.update

Geocode

  • ForwardRead-only

    Turn an address into coordinates, returning every match with its layer and confidence

    geocode.forward

  • ReverseRead-only

    Turn `latitude,longitude` into an address, with the admin layers that contain it

    geocode.reverse

Search

  • GeofencesRead-only

    Search geofences near a point, filtered by tag

    search.geofences

  • PlacesRead-only

    Search the places database near a point, filtered by chain or category within a radius

    search.places

Connect Radar to Claude, ChatGPT or Cursor

  1. 1

    Connect Radar in Corsair

    Add your Radar API key once in Corsair. Corsair stores the credential encrypted and makes the Radar API calls for your agent, so it never goes into a prompt or a config file. Connect Radar

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Radar. On a ChatGPT personal plan, connect Radar here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Radar's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/radar, add the Radar plugin, and connect with an API key. Then call methods like corsair.radar.api.events.conversion() from your app. Corsair keeps each tenant isolated.

Yes. Radar requires an API key from your Radar account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Radar, GitHub, Notion, Stripe, and the rest. Trigger Radar from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for location infrastructure with Radar - geocode addresses and coordinates, search places and geofences, read tracked users, geofences and trips, upsert a geofence, submit location updates and log conversions. Common builds include sync jobs, admin tooling, and agents that call Radar APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Radar API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/radar in the open repo. When Radar ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Radar data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Radar data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Radar on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive Radar operation. You can change a link's mode at hub.corsair.dev/me.