How to connect Radar to OpenClaw
Connect Radar to OpenClaw with ClawLink: paste your Radar key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine.
RadarAPI KEYMCPRadar is a full-stack location infrastructure platform offering SDKs and APIs for geofencing, location tracking, geocoding, search, routing, and maps.. Once connected, OpenClaw can read and act on Radar from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Radar access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Radar setup: install one ClawHub skill, connect Radar in the browser, and OpenClaw can call real Radar actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Radar.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Radar
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Radar?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Radar in the ClawLink dashboard — paste your Radar API key once.
Verify the connection by asking OpenClaw:
Use Radar to autocomplete address or place and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Radar is connected in the dashboard, that agent calls the same 37 Radar tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Radar MCP for OpenClaw
Looking for a Radar MCP server for OpenClaw? ClawLink connects Radar to OpenClaw and exposes 37 Radar tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Radar integration works the same way.
What the OpenClaw Radar integration can do
37 Radar tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 37.
30 of 37 Radar tools for OpenClaw
| Tool | What it does |
|---|---|
Autocomplete address or place radar_autocomplete_address_or_place | Autocomplete partial addresses and place names based on relevance and proximity |
Forward geocode radar_forward_geocode | Convert an address into geographic coordinates |
Get beacon radar_get_beacon | Retrieve a beacon by Radar _id |
Get beacon by tag radar_get_beacon_by_tag | Get a specific beacon by tag and external ID |
Get context for location radar_get_context_for_location | Retrieve context for a given location |
Get geofence radar_get_geofence | Retrieve a geofence by Radar _id or tag/externalId |
Get places settings radar_get_places_settings | Retrieve current Places settings for your Radar project |
Get route directions radar_get_route_directions | Get turn-by-turn directions between multiple locations |
Get route matrix radar_get_route_matrix | Calculate travel distance and duration between multiple origins and destinations for up to 625 |
Get trip radar_get_trip | Retrieve a trip by ID or externalId |
Get user radar_get_user | Get a user by Radar _id, userId, or deviceId |
Get users in geofence radar_get_users_in_geofence | Retrieve users currently within a specific geofence |
Ip geocode radar_ip_geocode | Geocode an IP address to city, state, and country |
List events radar_list_events | List events |
List geofences radar_list_geofences | List all geofences sorted by updated time |
List trips radar_list_trips | List all trips, sorted by updated time |
List users radar_list_users | List Radar users sorted by update time |
Reverse geocode radar_reverse_geocode | Convert geographic coordinates to structured addresses |
Route distance radar_route_distance | Compute distance and travel time between origins and destinations |
Search geofences near location radar_search_geofences_near_location | Search for geofences near a given location |
Search places near location radar_search_places_near_location | Search for places near given coordinates |
Search users near location radar_search_users_near_location | Search for users near a location |
Create beacon radar_create_beacon | Create a new beacon in Radar |
Create trip radar_create_trip | Create a new trip |
Track location update radar_track_location_update | Track a user's location update |
Update places settings radar_update_places_settings | Update Places settings for your Radar project including chain metadata preferences |
Update trip radar_update_trip | Update a trip |
Update trip by ID radar_update_trip_by_id | Update a trip status by Radar _id or external ID |
Upsert beacon by ID radar_upsert_beacon_by_id | Create or update a beacon by Radar _id |
Upsert beacon by tag radar_upsert_beacon_by_tag | Create or update a beacon by tag and externalId |
Try it: find the Radar tool you need
Browse the 30 Radar tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Radar to autocomplete address or place and walk me through the result in plain English.
Use Radar to forward geocode and walk me through the result in plain English.
Pull the relevant data from Radar, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Radar, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Radar working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Radar API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Radar account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Radar. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Radar actions to the runtime in a format your agent can reliably use. | 37 tools for Radar are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Radar to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Radar in the browser, and the 37 tools above work from chat. There is no SDK and no config file, and the Radar key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Radar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Radar, but the calls run through the ClawLink plugin and your connected account. Make sure Radar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Radar from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Radar tools
Radar tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Radar call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Radar returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Radar has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Radar integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Radar: link your Radar account once in the browser and OpenClaw can call the Radar API through 37 ready-made tools — no custom code or token handling.
How do I add Radar to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Radar skill from ClawHub, then you click Connect in the dashboard to authorize Radar. OpenClaw calls the tools from the next message — no config files, and the Radar key you paste is stored server-side instead of in your environment.
How long does it take to connect Radar to OpenClaw?
About two minutes. Sign in, click Connect next to Radar in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Radar up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Radar working from chat.
OpenClaw installed the Radar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Radar, but the calls run through the ClawLink plugin and your connected account. Make sure Radar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.