Strava MCP integration for AI agents.
Connect AI agents to Strava through 34 structured actions, including export route gpx, create activity, and explore segments. Review authentication, inputs…
- ACTION CONTRACTS
- 34
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Strava integration exposes
The Strava Agent App exposes 34 provider-backed actions for social work. Its current contract lets an authorized agent export the gpx content of a specified strava route, create a manually entered strava activity, and explore eligible strava segments within a given bounding box. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Strava account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Strava capabilities.
Showing 12 of 34 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
export_route_gpxREADExport the GPX content of a specified Strava route.
INPUTS: routeId
create_activityWRITECreate a manually entered Strava activity.
INPUTS: name / type / sportType / startDateLocal / elapsedTime
explore_segmentsREVIEWExplore eligible Strava segments within a given bounding box.
INPUTS: bounds / activityType / minCat / maxCat
export_route_tcxREADExport TCX content for a specified Strava route.
INPUTS: routeId
get_activityREADGet activity details for current Strava athlete by ID.
INPUTS: activityId / includeAllEfforts
get_activity_streamsREADGet stream data for the specified Strava activity.
INPUTS: activityId / keys / keyByType
get_activity_zonesREADGet the training zones for the specified Strava activity.
INPUTS: activityId
get_athlete_statsREADGet a summary of statistics for a specified Strava athlete.
INPUTS: athleteId
get_authenticated_athleteREADGet currently authenticated Strava athlete profile.
get_clubREADGet Strava club details by ID.
INPUTS: clubId
get_equipmentREADGet Strava gear details by ID.
INPUTS: gearId
get_routeREADGet Strava route details by ID.
INPUTS: routeId
INPUT CONTRACTS
Know what the action needs before it runs.
export_route_gpx
routeIdREQUIRED- Route ID.
create_activity
nameREQUIRED- Activity name.
typeOPTIONAL- Legacy activity type.
sportTypeREQUIRED- Activity sport type.
startDateLocalREQUIRED- Event start time.
elapsedTimeREQUIRED- Total time spent on the activity, in seconds.
explore_segments
boundsREQUIRED- Bounding box coordinates: south latitude, west longitude, north latitude, east longitude.
activityTypeOPTIONAL- Type of activities to explore.
minCatOPTIONAL- Minimum climb classification.
maxCatOPTIONAL- Maximum climb classification.
export_route_tcx
routeIdREQUIRED- Route ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Export Route Gpx
Export the GPX content of a specified Strava route. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
export_route_gpxControl Create Activity
Create a manually entered Strava activity. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_activityVerify with Export Route Tcx
Export TCX content for a specified Strava route. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
export_route_tcxSAFETY BOUNDARY
Operate Strava with explicit limits
- Authorize Strava with OAuth 2.0 and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `activity:write`, `read`, `activity:read`, and `profile:read_all`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Strava task completed successfully.
CONNECTION MODEL
OAuth 2.0
Strava uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 28
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Strava.