strava-mcp

Strava MCP Server

Strava workout records, routes, and segment efforts become accessible through Claude with strava-mcp. It serves runners, cyclists, and other Strava athletes who want to review training data, compare activity history, and export saved routes through conversational requests.

Server facts

strava-mcp

Project

Author
r-huijts
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
500
Last commit
Data as of

Overview

Training reviews can start with a recent Strava workout or a filtered activity history in Claude. strava-mcp retrieves activity details, lap records, photos, and time-series measurements such as heart rate, power, speed, and GPS coordinates. Athletes can examine individual sessions alongside their configured training zones, or retrieve their profile identifier to request recent, yearly, and lifetime statistics. Stream responses offer compact or verbose representations, with chunking and downsampling for larger datasets; available measurements depend on the activity.

Route planning and segment review use separate tools for browsing saved routes, inspecting route details, and exporting GPX or TCX files to a configured local directory. Segment tools support geographic discovery, inspecting individual segments, changing starred status, and reviewing the athlete's efforts with optional date filters. Club membership is also available. Account connection uses a browser authorization flow with Strava application credentials, which are stored locally. Users can check connection status or disconnect to remove stored credentials. The Node-based server communicates over stdio and includes setup instructions for Claude Desktop and Claude Code.

strava-mcp setup notes

  • strava-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers