Strava MCP Server
Related Servers
Alternatives to Strava MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceA Model Context Protocol server that provides language models with access to Strava API data, allowing them to query and analyze athlete activities from Strava.424MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables language models to interact with Strava data, including activities, athlete statistics, routes, achievements, and social features.6MIT
- 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.310MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables interaction with the Strava API v3 to manage fitness activities, athlete profiles, segments, and routes. It supports retrieving detailed performance metrics, exploring geographic data, and managing club information through natural language.58ISC
- AlicenseAqualityCmaintenanceA lightweight Garmin Model Context Protocol server with 12 curated endpoints for endurance athletes, enabling natural-language queries of activity, training, health, device, and goal data from Garmin Connect.12MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Strava integration, enabling LLMs to query activities, athlete stats, segments, routes, and perform training analysis.8MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_activity retrieves details of a specific activity, get_activity_segments focuses on segments within an activity, and get_user_activities lists the user's activities. The descriptions clearly differentiate these functions, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (get_activity, get_activity_segments, get_user_activities). The naming is predictable and readable, using 'get' as the verb throughout, which aligns well with the read-only nature of these tools.
With only 3 tools, this server feels under-scoped for a Strava integration, which typically involves activities, segments, athletes, and more. While the tools cover some read operations, the count is too low to support comprehensive agent workflows, such as creating or updating activities, which are common in fitness tracking domains.
The tool surface is severely incomplete for a Strava server, as it only includes read operations (get) with no support for create, update, or delete actions. There are significant gaps, such as missing tools for managing segments, athletes, or uploading activities, which will likely cause agent failures when attempting full interactions with the Strava API.