The whole surface is scoped to the authenticated athlete, so this reads your own history rather than researching anyone else's. Authentication is handled in-band — connect-strava opens a browser, disconnect-strava removes the stored credentials — so there is no key to place in a config file before the first call. Route export is the one operation that writes to your machine, and it targets a directory that has to be configured beforehand.
A Strava client scoped to the authenticated athlete: activities and their raw streams, segments and efforts, routes, and the account connection itself.
- Activity history at three grains: the most recent, the complete history filtered by date range and activity or sport type, and one activity in full detail
- Time-series streams from an activity — heart rate, power, speed, GPS coordinates — at a density you choose from about 100 points to about 10,000, with pagination
- Lap-by-lap data for an activity, and the athlete's own configured heart-rate and power zones
- The athlete profile with the numeric id the stats tools need, and recent, year-to-date and all-time statistics for it
- Segments end to end: the ones you starred, a specific segment or effort, your efforts on a segment across a date window, and starring or unstarring
- Segment discovery inside a geographical bounding box, narrowed by activity type and climb category
- Routes you created, exported as GPX or TCX into a pre-configured local directory, plus the photos attached to an activity at a pixel size you name
A Strava account you authorise in a browser — connect-strava opens the window and stores the credentials, check-strava-connection reports the state. Route exports need a local directory configured in advance.
One command plus a key — npm install -g @r-huijts/strava-mcp-server, then supply credentials