Authenticate a user via Strava OAuth and upload a completed activity (FIT/TCX/GPX) on their behalf
domain: developers.strava.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an API application in Strava's API settings to get a client ID and client secret
Redirect the user to Strava's OAuth authorize endpoint requesting the activity:write scope (plus activity:read or activity:read_all if you also need to read data)
Exchange the returned authorization code for an access token and refresh token via the token endpoint
POST the activity file (FIT, TCX, or GPX) as multipart/form-data to the uploads endpoint using the athlete's access token
Poll the returned upload ID against the upload status endpoint until processing completes and an activity ID is returned
Known gotchas
activity:write only grants create/edit access to activities visible to your app per the athlete's read access level — it does not grant broader read access
Uploads are processed asynchronously; you must poll the upload status endpoint rather than expecting an immediate activity ID
Strava introduced a paid developer tier structure in 2026 with tier-based rate limits — check your app's actual dashboard limits rather than assuming defaults
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?