Server facts
strava-mcp
Project
- Author
- davidmosiah
- Repository
- github.com/davidmosiah/strava-mcp
- License
- Not specified
- Category
- Data & Analytics
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- Typescript
- activities
- ai agents
- claude mcp
- cycling
- fitness
- mcp
- running
- strava
- training
Overview
Training reviews in Claude, Cursor and other MCP-compatible clients can draw on Strava activity history through this unofficial, local-first connector. Tools retrieve activity details, athlete zones, aggregate statistics, routes, clubs and equipment. Daily summaries describe recent training load, while weekly scorecards cover volume, intensity, sport mix and possible next-week actions. For closer investigation, strava_activity_series combines statistics calculated from full-resolution samples with a downsampled metric series capped at 500 points. That tool never returns GPS, making it distinct from the separate activity-stream tool.
Connection checks inspect local configuration, token availability and cache readiness without contacting Strava. Setup guidance and OAuth tools support account connection, while privacy audits report local settings without disclosing secrets. Tokens stay in local storage and are not included in tool responses; an optional SQLite cache is available. GPS access through the stream tool requires explicit user intent, and route geometry is redacted outside raw mode. Shared Delx Wellness profile tools support onboarding and confirmed profile updates without changing GPS defaults. The connector supports personal training analysis, not medical advice or training prescription.
strava-mcp setup notes
- strava-mcp records stdio only; confirm a network transport upstream before planning remote access.
- strava-mcp has no recorded license; confirm reuse terms in its repository.