Summary
Your own training log, readable where you are already asking questions about it.
Four read tools, all scoped to the authenticated athlete: nothing uploads, edits or reaches segments, kudos or other people's rides. Three of the four differ only in how you express when, so the practical gain is that a question about last March costs one call and a follow-up on one ride costs a second.
What it is
A four-tool read of the authenticated athlete's Strava activities, by recency, by date range, or by activity ID.
What you get
- get_activities returns the most recent activities, 10 by default
- get_activities_by_date_range takes ISO start and end dates and returns up to 30 by default
- get_recent_activities looks back a number of days, 7 by default
- get_activity_by_id returns the detail for a single activity
Requirements
STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET and STRAVA_REFRESH_TOKEN for the athlete whose activities you want to read.
Setup effort
One command plus a key — uvx strava-mcp-server, then supply credentials