strava-activity-mcp-server

An MCP server package intended to let an AI agent access Strava activity data by exposing MCP tools/endpoints for querying and retrieving Strava activities (e.g., listing activities, fetching activity details), likely using Strava’s API and an OAuth-based connection.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Ai Ml mcp strava fitness activities api-integration ai-agent
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
52
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
40
Error Messages
0
Auth Simplicity
55
Rate Limits
25

🔒 Security

TLS Enforcement
60
Auth Strength
60
Scope Granularity
40
Dep. Hygiene
50
Secret Handling
50

Security depends heavily on the MCP server implementation: correct OAuth redirect flow, secure token storage/refresh, and safe logging are critical. TLS is typically required for Strava API calls, but the provided input does not confirm implementation details.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
30
AF Security Reliability

Use Cases

  • • Summarize a user’s recent Strava activities for coaching/analytics
  • • Retrieve and analyze activity details (distance, duration, type, start date) for reports
  • • Automate fitness check-ins or trend monitoring from Strava data
  • • Build agent workflows that respond to user questions about past workouts

Not For

  • • Handling real-time streaming events (Strava is polled via API; MCP tools are request/response)
  • • Replacing full BI/warehouse ingestion pipelines without additional infrastructure
  • • Use as a general-purpose Strava admin tool (likely scoped to read/query activities)
  • • Security-sensitive production deployments without verifying OAuth/token handling in the implementation

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: OAuth2 (likely, via Strava) for user authorization
OAuth: Yes Scopes: No

OAuth is expected for Strava access; the schema above cannot confirm exact scope names/requirements from the provided input.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Agents may assume pagination/filtering exists for large activity histories; confirm tool parameters/limits.
  • ⚠ OAuth/token expiration can cause failures; confirm refresh/token-expiry handling behavior.

Alternatives

Direct use of the Strava Web API from your own backend (OAuth + REST) Third-party analytics integrations that already normalize Strava activity data Other MCP servers or agent toolkits that wrap Strava endpoints (if available)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for strava-activity-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered