The Strava MCP Server connects to your Strava account, allowing you to interact with your Strava data using natural language queries.
From the registry: MCP server for accessing Strava API

Please install the `strava-mcp-rhuijts` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js** — Node.js required Run: `node -v` (https://nodejs.org/)
- **Strava API credentials** — Create a free Strava API app at strava.com/settings/api with callback domain set to localhost. Then connect via Claude by saying 'Connect my Strava account'. (https://www.strava.com/settings/api)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@r-huijts/strava-mcp-server"]
- optional environment variables:
- `STRAVA_CLIENT_ID`: Strava API Client ID (alternative to browser OAuth setup) (example: `<your_client_id>`)
- `STRAVA_CLIENT_SECRET`: Strava API Client Secret (example: `<your_client_secret>`)
- `STRAVA_ACCESS_TOKEN`: OAuth access token (example: `<your_access_token>`)
- `STRAVA_REFRESH_TOKEN`: OAuth refresh token (example: `<your_refresh_token>`)
- `ROUTE_EXPORT_PATH`: Directory for GPX/TCX route exports (example: `~/Downloads`)
Note: 25 tools for Strava: activities, stats, segments, routes, clubs, gear. Browser-based OAuth setup (say 'Connect my Strava account') or set env vars directly. Tokens auto-refresh and cached at ~/.config/strava-mcp/config.json.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.STRAVA_CLIENT_IDrequiredYour Strava Application Client ID.STRAVA_CLIENT_SECRETrequiredYour Strava Application Client Secret.STRAVA_ACCESS_TOKENrequiredOAuth access token.STRAVA_REFRESH_TOKENrequiredOAuth refresh token.