Strava MCP Server
Related Servers
Alternatives to Strava MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables language models to interact with Strava data, including activities, athlete statistics, routes, achievements, and social features.6MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables users to access Strava fitness data, including user activities, activity details, segments, and leaderboards through a structured API interface.34MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Strava integration, enabling LLMs to query activities, athlete stats, segments, routes, and perform training analysis.9MIT
- AlicenseBqualityCmaintenanceA local, read-only Model Context Protocol server for an athlete's Strava profile and activities, enabling retrieval of profile data, activity lists (with paging and date filters), and detailed activity information via standard input/output for MCP hosts.311 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides language models with access to personal Whoop fitness data, allowing queries for cycles, recovery, strain, and workout information from the Whoop API.26-
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.4836MIT
TDQS
Scored across 4 tools
Multiple tools have overlapping purposes that could cause confusion. get_activities and get_recent_activities both retrieve recent activities with similar parameters, while get_activities_by_date_range provides date-based filtering that could also be used for recent activities. Only get_activity_by_id has a clearly distinct purpose.
All tool names follow a consistent verb_noun pattern with snake_case formatting. The naming is perfectly consistent across all four tools, making them predictable and easy to understand at a glance.
With only 4 tools, this feels thin for a Strava server that presumably handles athlete activities. While the count is reasonable for a minimal implementation, it lacks coverage for other Strava domains like segments, clubs, or athlete profiles that would be expected.
The tool surface is severely incomplete for a Strava integration. While it provides multiple ways to read activities, there are no tools for creating, updating, or deleting activities, nor any coverage of other Strava resources like segments, clubs, gear, or athlete statistics. This creates significant gaps that will limit agent capabilities.