Can I use Radar as a CLI?

Yes. KosmoKrator exposes a Radar CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Radar through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Radar tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Radar credentials stored?

Radar credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Radar MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Radar CLI for AI Agents

Use the Radar CLI from KosmoKrator to call Radar tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Submit Radar feedback View package source

Radar CLI Setup

Radar can be configured headlessly with `kosmokrator integrations:configure radar`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure radar --set access_token="$RADAR_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor radar --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`RADAR_ACCESS_TOKEN`	Secret `secret`	yes	API Key
`url`	`RADAR_URL`	URL `url`	no	API Base URL

Call Radar Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call radar.radar_list_geofences '{
  "limit": 1,
  "cursor": "example_cursor",
  "tag": "example_tag",
  "group": "example_group"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:radar radar_list_geofences '{
  "limit": 1,
  "cursor": "example_cursor",
  "tag": "example_tag",
  "group": "example_group"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs radar --json
kosmo integrations:docs radar.radar_list_geofences --json
kosmo integrations:schema radar.radar_list_geofences --json
kosmo integrations:search "Radar" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Radar.

`radar.radar_list_geofences`

Read read

List geofences from Radar with optional filters for tag, group, and pagination.

Parameters: limit, cursor, tag, group

Generic CLI call

kosmo integrations:call radar.radar_list_geofences '{"limit":1,"cursor":"example_cursor","tag":"example_tag","group":"example_group"}' --json

Provider shortcut

kosmo integrations:radar radar_list_geofences '{"limit":1,"cursor":"example_cursor","tag":"example_tag","group":"example_group"}' --json

`radar.radar_get_geofence`

Read read

Retrieve detailed information about a specific geofence by its ID.

Parameters: geofence_id

Generic CLI call

kosmo integrations:call radar.radar_get_geofence '{"geofence_id":"example_geofence_id"}' --json

Provider shortcut

kosmo integrations:radar radar_get_geofence '{"geofence_id":"example_geofence_id"}' --json

`radar.radar_create_geofence`

Write write

Create a new geofence in Radar with a name, type, and geometry.

Parameters: name, description, type, coordinates, radius, tag, group, external_id, metadata

Generic CLI call

kosmo integrations:call radar.radar_create_geofence '{"name":"example_name","description":"example_description","type":"example_type","coordinates":"example_coordinates","radius":1,"tag":"example_tag","group":"example_group","external_id":"example_external_id"}' --json

Provider shortcut

kosmo integrations:radar radar_create_geofence '{"name":"example_name","description":"example_description","type":"example_type","coordinates":"example_coordinates","radius":1,"tag":"example_tag","group":"example_group","external_id":"example_external_id"}' --json

`radar.radar_list_users`

Read read

List users from Radar with optional filters for tags and pagination.

Parameters: limit, cursor, tags

Generic CLI call

kosmo integrations:call radar.radar_list_users '{"limit":1,"cursor":"example_cursor","tags":"example_tags"}' --json

Provider shortcut

kosmo integrations:radar radar_list_users '{"limit":1,"cursor":"example_cursor","tags":"example_tags"}' --json

`radar.radar_get_user`

Read read

Retrieve detailed information about a specific Radar user by their ID.

Parameters: user_id

Generic CLI call

kosmo integrations:call radar.radar_get_user '{"user_id":"example_user_id"}' --json

Provider shortcut

kosmo integrations:radar radar_get_user '{"user_id":"example_user_id"}' --json

`radar.radar_list_events`

Read read

List events from Radar with optional filters for type, user, and pagination.

Parameters: limit, cursor, type, user_id, geofence_id

Generic CLI call

kosmo integrations:call radar.radar_list_events '{"limit":1,"cursor":"example_cursor","type":"example_type","user_id":"example_user_id","geofence_id":"example_geofence_id"}' --json

Provider shortcut

kosmo integrations:radar radar_list_events '{"limit":1,"cursor":"example_cursor","type":"example_type","user_id":"example_user_id","geofence_id":"example_geofence_id"}' --json

`radar.radar_get_current_user`

Read read

Get the currently authenticated Radar user's account information.

Parameters: none

Generic CLI call

kosmo integrations:call radar.radar_get_current_user '{}' --json

Provider shortcut

kosmo integrations:radar radar_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`radar.radar_list_geofences`

List geofences from Radar with optional filters for tag, group, and pagination.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_list_geofences --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of results to return (default: 100, max: 1000)
`cursor`	string	no	Pagination cursor from a previous response
`tag`	string	no	Filter geofences by tag
`group`	string	no	Filter geofences by group identifier

`radar.radar_get_geofence`

Retrieve detailed information about a specific geofence by its ID.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_get_geofence --json

Parameter	Type	Required	Description
`geofence_id`	string	yes	The unique identifier of the geofence to retrieve.

`radar.radar_create_geofence`

Create a new geofence in Radar with a name, type, and geometry.

Operation: Write write
Schema command: kosmo integrations:schema radar.radar_create_geofence --json

Parameter	Type	Required	Description
`name`	string	yes	The name of the geofence.
`description`	string	no	A description of the geofence.
`type`	string	no	The geofence type, e.g. "circle", "polygon", or "isochrone".
`coordinates`	string	no	GeoJSON coordinates or a center point (e.g. "lat,lng").
`radius`	integer	no	Radius in meters (for circle geofences).
`tag`	string	no	A tag to categorize the geofence.
`group`	string	no	A group identifier for the geofence.
`external_id`	string	no	An optional external ID for mapping to your own records.
`metadata`	object	no	Optional custom metadata key-value pairs.

`radar.radar_list_users`

List users from Radar with optional filters for tags and pagination.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_list_users --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of results to return (default: 100, max: 1000)
`cursor`	string	no	Pagination cursor from a previous response
`tags`	string	no	Filter users by tags (comma-separated)

`radar.radar_get_user`

Retrieve detailed information about a specific Radar user by their ID.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_get_user --json

Parameter	Type	Required	Description
`user_id`	string	yes	The unique identifier of the user to retrieve.

`radar.radar_list_events`

List events from Radar with optional filters for type, user, and pagination.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_list_events --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of results to return (default: 100, max: 1000)
`cursor`	string	no	Pagination cursor from a previous response
`type`	string	no	Filter by event type, e.g. "user.entered_geofence", "user.exited_geofence"
`user_id`	string	no	Filter events by user ID
`geofence_id`	string	no	Filter events by geofence ID

`radar.radar_get_current_user`

Get the currently authenticated Radar user's account information.

Operation: Read read
Schema command: kosmo integrations:schema radar.radar_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.