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 CI

Use the Radar CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Radar feedback View package source

Radar CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Radar CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Radar CLI for CI
kosmokrator integrations:configure radar --set access_token="$RADAR_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call radar.radar_list_geofences '{"limit":1,"cursor":"example_cursor","tag":"example_tag","group":"example_group"}' --json

Discovery Before Execution

Agents and scripts can inspect Radar docs and schemas 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

Useful Radar CLI Functions

Function	Type	Parameters	Description
`radar.radar_list_geofences`	Read	limit, cursor, tag, group	List geofences from Radar with optional filters for tag, group, and pagination.
`radar.radar_get_geofence`	Read	geofence_id	Retrieve detailed information about a specific geofence by its ID.
`radar.radar_create_geofence`	Write	name, description, type, coordinates, radius, tag, group, external_id, metadata	Create a new geofence in Radar with a name, type, and geometry.
`radar.radar_list_users`	Read	limit, cursor, tags	List users from Radar with optional filters for tags and pagination.
`radar.radar_get_user`	Read	user_id	Retrieve detailed information about a specific Radar user by their ID.
`radar.radar_list_events`	Read	limit, cursor, type, user_id, geofence_id	List events from Radar with optional filters for type, user, and pagination.
`radar.radar_get_current_user`	Read	none	Get the currently authenticated Radar user's account information.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Radar CLI Pages

Cron Jobs Radar CLI for cron jobs. Shell Scripts Radar CLI for shell scripts. Headless Automation Radar CLI for headless automation. Coding Agents Radar CLI for coding agents.