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 Claude Agent SDK

Connect Radar to Claude Agent SDK 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 Claude Agent SDK

Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server.

Add a KosmoKrator stdio MCP server to the Claude Agent SDK options. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Agent SDK can inspect read-capable tools without receiving write access by default.

Radar MCP Config for Claude Agent SDK

Use a narrow integration list so the agent does not load unrelated tools.

{
  "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 Claude Agent SDK

Claude Agent SDK 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 Claude Agent SDKClient-level gateway setup.