Strava MCP Server (via HAPI)
MCP server for Strava fitness platform — enabling AI agents to access athletes, activities, segments, clubs, and routes. Built via the HAPI MCP framework wrapping the Strava API. Enables fitness analysis agents to retrieve workout data, performance metrics, and social fitness features.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
GPS location data is highly sensitive — reveals precise movement patterns. OAuth with read-only scopes. GDPR compliance for EU athletes.
⚡ Reliability
Best When
A fitness enthusiast or coach wants AI agents to analyze Strava workout data — identifying trends, comparing performances, and generating training insights from activity history.
Avoid When
You don't use Strava. Strava API requires OAuth and has strict commercial use restrictions. Health data from fitness activities is sensitive.
Use Cases
- • Analyzing Strava activity history and performance trends from fitness coaching agents
- • Retrieving athlete activity stats for personalized training recommendations
- • Monitoring segment and route data for athletic performance agents
- • Building fitness analytics dashboards using Strava data in AI workflows
Not For
- • Non-Strava fitness platforms (Strava-specific)
- • Real-time GPS tracking (API-based post-activity access)
- • Bulk data exports for commercial fitness products (Strava API terms)
Interface
Authentication
Strava OAuth 2.0. Athlete must authorize access. Use read-only scopes for analytics. activity:read for basic; activity:read_all for private activities.
Pricing
Strava API free for approved apps. Rate limits apply. MCP server is free open source. Commercial use requires Strava API agreement compliance.
Agent Metadata
Known Gotchas
- ⚠ PRIVACY: Strava data includes GPS routes which can reveal home/work locations
- ⚠ OAuth token refresh required for long-running fitness analysis agents
- ⚠ Strict rate limits (100 req/15min) — batch-heavy agents will be throttled
- ⚠ Private activities and hide-segments features must be respected
- ⚠ HAPI framework intermediary — validate that the implementation matches current Strava API
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Strava MCP Server (via HAPI).
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.