Strava

🔑 BYO Key — Health

Read-only access to Strava activity data — distance, duration, heart rate, sport type. Auto-refreshes OAuth tokens.

🔑 Setup Required — Bring Your Own Key This integration requires API credentials. Store them once via setup_integration or the Dashboard Vault — they're encrypted with AES-256-GCM and never exposed.

Required Credentials

strava_client_id

Client ID

Your Strava API application Client ID. Find it at https://www.strava.com/settings/api

strava_client_secret

Client Secret

40-character hex secret from your Strava API application page.

strava_access_token

Access Token

Initial access_token from the OAuth authorization_code exchange. The engine rotates this automatically.

strava_refresh_token

Refresh Token

Initial refresh_token from the OAuth authorization_code exchange. The engine rotates this automatically.

strava_token_expires_at

Token Expires At (unix timestamp)

Unix timestamp at which the access_token expires. Provided by Strava in the OAuth response.

Get your API key at www.strava.com →

Endpoints (3)

GET athlete

Get authenticated athlete info (firstname, lastname, country, etc.). Useful as a token validation check.

No input parameters required.

GET list-activities

List athlete activities. before/after are unix timestamps for date filtering. page/per_page for pagination (max per_page=200). Returns array of activity summaries.

Field	Type	Required
`before`	integer	No
`after`	integer	No
`page`	integer	No
`per_page`	integer	No

GET get-activity

Get full detail for a single activity by Strava activity ID. Includes description, splits, segments, gear, and detailed metrics.

Field	Type	Required	Description
`activity_id`	integer	✓ Yes
`include_all_efforts`	boolean	No

MCP Tool Names

When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:

Endpoint	MCP Tool Name
athlete	`strava_athlete`
list-activities	`strava_list_activities`
get-activity	`strava_get_activity`

← Back to all integrations