OpenAthlete
Related Servers
Alternatives to OpenAthlete
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that mirrors your Garmin data into a personal database and exposes tools for health summaries, training load, muscle readiness, and race analysis, with optional chat-driven insights via stdio or HTTP.1MIT
- AlicenseAqualityBmaintenanceA hosted MCP server that connects a user's own Garmin Connect account to AI agents, enabling them to read training, sleep, HRV, and other metrics and to create and schedule workouts. It works with Claude Code, ChatGPT, Cursor, and other MCP-compatible clients without a Garmin Connect API key.7104 PyPIElastic 2.0
- AlicenseBqualityBmaintenanceA read-only MCP server that lets AI agents query a user's own Garmin Connect data via Garmin's official Personal API. It exposes activities, daily wellness metrics, sleep and recovery, and body/profile data as tools for natural-language analysis.21Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that transforms Garmin data into compact, verdict-first coaching reports for LLMs, computing metrics like CTL/ATL/TSB and ACWR to answer training readiness questions.1461 PyPIApache 2.0
- AlicenseAqualityBmaintenanceMCP server that connects AI agents to Intervals.icu, enabling access to training data such as activities, wellness metrics, calendar events, gear, power curves, and custom items. Includes a running coach AI template for automated post-session analysis.191MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for TrainingPeaks that reads workouts, fitness metrics (CTL/ATL/TSB), and health data, and creates/updates/deletes planned workouts. Enables AI-powered training plan management and automated adjustment based on performance, fatigue, and injury.-
TDQS
Scored across 9 tools
The tools mostly target distinct resources and actions. The only overlap is get_overview, which summarizes training load/recovery and may trigger sync, versus the specialized get_training_load, get_recovery_status, and sync_now; descriptions make the summary-vs-detail boundary clear enough.
All names use lowercase snake_case and are predominantly verb_noun patterns such as get_*, query_*, read_*, write_*, and create_*. sync_now is the only non-noun object but remains clear and consistent.
Nine tools is a good fit for a focused athlete-assistant surface. Each tool covers a distinct workflow, and there is no obvious redundancy or missing low-level utility.
Core read, sync, memory, and workout-creation workflows are covered. Notable gaps remain around the workout lifecycle (no update/delete and no explicit list/get workout) and plan mutation, though these may be delegated to platform MCPs.