Integration

Strava integration

Strava API v3 for athletes, activities, segments, routes, clubs and gear. Read and write training data for the authenticated athlete: list and create activities, inspect laps, kudos, comments and heart-rate/power zones, explore and star segments, browse club feeds, and upload activity files (GPX, TCX, FIT). All calls are scoped to the OAuth-connected athlete.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Strava.Built from the 26 Strava tools below, on the connection you add once.

Common Strava use cases

  • importing workouts from another platform
  • computing training load
  • auditing club membership
  • analysing interval workouts
  • building a club leaderboard
  • posting a weekly club digest
  • enriching a training log entry
  • sending a route to a GPS device
  • building a yearly training report
  • suggesting climbs near a location

What you can do with Strava

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Activity, 5 operations

  • create_activityCreate activityPOSTCreates a manual Strava activity from a title, sport type, start time and duration.
  • get_activityGet activityGETRetrieves one activity in full detail, optionally including every segment effort.
  • list_athlete_activitiesList athlete activitiesGETLists the authenticated athlete's activities, newest first, with optional time window and pagination.
  • list_club_activitiesList club activitiesGETLists activities recently posted by members of a club.
  • update_activityUpdate activityPUTUpdates the title, description, sport type, gear or flags of an existing activity.

Route, 3 operations

  • export_route_gpxExport route gpxGETExports a Strava route as a GPX file ready for a downstream node.
  • get_routeGet routeGETRetrieves one route with its distance, elevation, estimated time and encoded polyline.
  • list_athlete_routesList athlete routesGETLists the routes an athlete has created, with distance, elevation and type.

Segment, 3 operations

  • explore_segmentsExplore segmentsGETFinds up to ten popular segments inside a latitude/longitude bounding box.
  • get_segmentGet segmentGETRetrieves one segment with its distance, grade, elevation profile and popularity counts.
  • list_starred_segmentsList starred segmentsGETLists the segments the authenticated athlete has starred.

Athlete, 2 operations

  • get_authenticated_athleteGet authenticated athleteGETRetrieves the profile of the currently authenticated Strava athlete.
  • update_authenticated_athleteUpdate authenticated athletePUTUpdates the authenticated athlete's weight in kilograms.

Club, 2 operations

  • get_clubGet clubGETRetrieves one club with its description, sport, location and member count.
  • list_athlete_clubsList athlete clubsGETLists the clubs the authenticated athlete has joined.

Upload, 2 operations

  • get_uploadGet uploadGETChecks whether an uploaded activity file has finished processing.
  • upload_activityUpload activityPOSTUploads a GPX, TCX or FIT file that Strava turns into an activity asynchronously.

Zone, 2 operations

  • get_activity_zonesGet activity zonesGETRetrieves the heart-rate and power zone time distribution of an activity.
  • get_athlete_zonesGet athlete zonesGETRetrieves the authenticated athlete's heart-rate and power training zones.

Comment, 1 operation

  • list_activity_commentsList activity commentsGETLists the comments left on a Strava activity.

Gear, 1 operation

  • get_gearGet gearGETRetrieves one bike or pair of shoes with its total logged distance.

Kudos, 1 operation

  • list_activity_kudoersList activity kudoersGETLists the athletes who gave kudos to an activity.

Lap, 1 operation

  • list_activity_lapsList activity lapsGETLists the laps of an activity with per-lap distance, time, speed, heart rate and power.

Member, 1 operation

  • list_club_membersList club membersGETLists the members of a club with their admin and owner flags.

Segment effort, 1 operation

  • get_segment_effortGet segment effortGETRetrieves one segment effort with its time, power, heart rate and leaderboard ranks.

Stat, 1 operation

  • get_athlete_statsGet athlete statsGETRetrieves recent, year-to-date and all-time activity totals for an athlete.

OAuth scopes Strava requires

Each operation declares the scopes Strava requires for it.

  • readneeded by explore_segments, export_route_gpx, get_athlete_stats and 8 more
  • activity:readneeded by get_activity, get_activity_zones, get_segment_effort and 4 more
  • activity:writeneeded by create_activity, get_upload, update_activity and 1 more
  • profile:read_allneeded by get_athlete_zones, get_gear
  • profile:writeneeded by update_authenticated_athlete

Use Strava from Claude Code, Cursor or Codex

Connect Strava in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Strava operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Strava

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Strava once

    Add your Strava connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Strava integration FAQ

What can you do with the Strava integration?

LiveContext exposes 26 operations on Strava, covering activity, route, segment and athlete. Common uses include importing workouts from another platform, computing training load and auditing club membership.

Which OAuth scopes does Strava require?

It depends on the operation: each one declares the scopes Strava requires for it. The most common are read (11 operations), activity:read (7 operations), activity:write (4 operations) and profile:read_all (2 operations).

Popular integrations

Browse the whole catalog