Can I use Strava as a CLI?

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

Can I expose Strava through MCP?

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

Where are Strava credentials stored?

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

Can I deny write access for Strava MCP tools?

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

other

Strava CLI for Headless Automation

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

6 functions 5 read 1 write Bearer token auth

Submit Strava feedback View package source

Strava 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 Strava CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Strava CLI for Headless Automation
kosmokrator integrations:configure strava --set access_token="$STRAVA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call strava.strava_create_activity '{"name":"example_name","type":"example_type","start_date_local":"example_start_date_local","elapsed_time":1,"description":"example_description","distance":1,"trainer":1,"commute":1}' --json

Discovery Before Execution

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

kosmo integrations:docs strava --json
kosmo integrations:docs strava.strava_create_activity --json
kosmo integrations:schema strava.strava_create_activity --json
kosmo integrations:search "Strava" --json
kosmo integrations:list --json

Useful Strava CLI Functions

Function	Type	Parameters	Description
`strava.strava_create_activity`	Write	name, type, start_date_local, elapsed_time, description, distance, trainer, commute	Create a manual activity on Strava. Requires a name, activity type, start date, and elapsed time in seconds.
`strava.strava_get_activity`	Read	activity_id	Get detailed information about a specific Strava activity, including distance, pace, elevation, and splits.
`strava.strava_get_athlete`	Read	none	Get the authenticated athlete's Strava profile — name, location, follower/following counts, and stats.
`strava.strava_get_current_user`	Read	none	Get the current authenticated user's Strava profile. This is an alias for strava_get_athlete — returns name, location, follower/following counts, and stats.
`strava.strava_list_activities`	Read	page, per_page, before, after	List recent activities for the authenticated Strava athlete. Supports pagination and date filtering with before/after Unix timestamps.
`strava.strava_list_clubs`	Read	page, per_page	List clubs the authenticated Strava athlete belongs to. Returns club names, member counts, and sport types.

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

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