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 MCP Integration for Codex

Connect Radar to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Radar feedback View package source

Connect Radar to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Radar MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-radar": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=radar",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=radar --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Radar instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Radar Tools Visible to Codex

Codex sees stable MCP tool names generated from the Radar integration catalog.

MCP tool	Source function	Type	Description
`integration__radar__radar_list_geofences`	`radar.radar_list_geofences`	Read	List geofences from Radar with optional filters for tag, group, and pagination.
`integration__radar__radar_get_geofence`	`radar.radar_get_geofence`	Read	Retrieve detailed information about a specific geofence by its ID.
`integration__radar__radar_create_geofence`	`radar.radar_create_geofence`	Write	Create a new geofence in Radar with a name, type, and geometry.
`integration__radar__radar_list_users`	`radar.radar_list_users`	Read	List users from Radar with optional filters for tags and pagination.
`integration__radar__radar_get_user`	`radar.radar_get_user`	Read	Retrieve detailed information about a specific Radar user by their ID.
`integration__radar__radar_list_events`	`radar.radar_list_events`	Read	List events from Radar with optional filters for type, user, and pagination.
`integration__radar__radar_get_current_user`	`radar.radar_get_current_user`	Read	Get the currently authenticated Radar user's account information.

Related Radar Pages

Radar CLIUse direct JSON commands instead of MCP discovery. Radar MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.