Can I use Samsara as a CLI?

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

Can I expose Samsara through MCP?

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

Where are Samsara credentials stored?

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

Can I deny write access for Samsara MCP tools?

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

other

Samsara CLI for Headless Automation

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

6 functions 6 read 0 write Bearer token auth

Submit Samsara feedback View package source

Samsara CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Samsara CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Samsara CLI for Headless Automation
kosmokrator integrations:configure samsara --set access_token="$SAMSARA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call samsara.samsara_list_vehicles '{"limit":1,"after":"example_after"}' --json

Discovery Before Execution

Agents and scripts can inspect Samsara docs and schemas before choosing a function.

kosmo integrations:docs samsara --json
kosmo integrations:docs samsara.samsara_list_vehicles --json
kosmo integrations:schema samsara.samsara_list_vehicles --json
kosmo integrations:search "Samsara" --json
kosmo integrations:list --json

Useful Samsara CLI Functions

Function	Type	Parameters	Description
`samsara.samsara_list_vehicles`	Read	limit, after	List fleet vehicles from Samsara. Returns vehicle details including name, VIN, make, model, year, and GPS location. Supports pagination.
`samsara.samsara_get_vehicle`	Read	id	Get detailed information about a specific vehicle by its Samsara ID, including name, VIN, make, model, year, GPS location, and odometer reading.
`samsara.samsara_list_drivers`	Read	limit, after	List fleet drivers from Samsara. Returns driver details including name, username, email, phone, and driver license info. Supports pagination.
`samsara.samsara_get_driver`	Read	id	Get detailed information about a specific driver by their Samsara ID, including name, username, email, phone, and driver license details.
`samsara.samsara_list_sensors`	Read	limit, after	List IoT sensors from Samsara. Returns sensor details including name, type, model, connectivity, and current readings. Supports pagination.
`samsara.samsara_get_current_user`	Read	none	Get the currently authenticated Samsara user profile, including name, email, role, and organization details.

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 Samsara CLI Pages

CI Samsara CLI for CI. Cron Jobs Samsara CLI for cron jobs. Shell Scripts Samsara CLI for shell scripts. Coding Agents Samsara CLI for coding agents.