Strava MCP Server

Strava

Strava data is scoped to the authenticated athlete. Start with the athlete profile for identity, get activities for workout history or one workout's detailed metadata, and request streams only when time-series analysis is needed.

Data Model

• Athlete — the authenticated user. Athlete stats use this ID and summarize activity totals.
• Activities — workouts such as runs, rides, swims, hikes, and walks. Activity summaries are enough for recent-history questions; detailed activity reads add map, gear, split, and segment-effort context.
• Streams — time-series samples for an activity or route, such as time, distance, altitude, speed, heart rate, cadence, watts, coordinates, and moving state.
• Clubs — athlete memberships and club detail, with optional club activities, administrators, and members when a club ID is known.
• Gear — bikes and shoes referenced by athlete profile or activity detail responses.
• Routes — planned routes created by the athlete. Private routes can be filtered out by Strava when private-route access is not granted.
• Segments — starred, discovered, or explicitly fetched climbs, sprints, and route sections. Segment efforts are athlete-specific attempts and can require a Strava subscription.

Workflows

1. Recent training summary: Get the athlete, get activities with a small per_page, group by sport_type or type, and summarize distance, moving time, elevation, and start dates.
2. Single-workout analysis: Get activities, pick the target activity ID, get the same activity with that ID for details, then use laps or streams only if the question needs splits, pacing, heart-rate, cadence, power, route, or elevation trends.
3. Aggregate performance: Use athlete stats for all-time, year-to-date, and recent totals. Use activities instead when the question needs individual workouts or date-windowed trends.
4. Route and segment context: Get routes or segments when the athlete asks about planned routes, favorite segments, geographic discovery, or route/segment metadata.
5. Clubs and equipment: Get clubs for social/team context; fetch gear only after an athlete or activity response exposes a bike or shoe ID.

Gotchas

• Athlete-scoped: All results are for the authenticated athlete. Strava does not provide cross-athlete access through this bundle.
• Read-only: This provider is configured for read access. Do not attempt activity creation, activity edits, uploads, or segment star/unstar actions.
• Activity visibility: Activities marked Only Me appear only when the authorized Strava connection includes private activity access.
• Activity pagination: Use one starting-position parameter at a time for activity listing: before, after, or page. after returns activities oldest first from that timestamp; default ordering is newest first.
• Stats visibility: Athlete stats include only activities Strava counts for that stats endpoint, which can differ from the full activity list.
• Streams can be sparse: Strava returns only streams recorded for the activity. Heart rate, cadence, power, temperature, and GPS streams can be absent.
• Subscription and private-data gates: Activity zones, athlete zones, private routes, private segments, and segment efforts can return upstream permission errors even when ordinary activity reads work.
• Exports are XML: Route GPX and TCX exports return text/XML bodies, not JSON route objects.