enduraw-MCP
Related Servers
Alternatives to enduraw-MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceTurns any AI assistant into a physiological AI running coach by abstracting fitness APIs and exposing 70+ structured analytical MCP tools based on endurance models.21MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query Garmin training and recovery data—including activities, laps, strength sets, sleep, HRV, stress, and Body Battery—through the official read-only Garmin Connect Personal API. It also enables generating training dashboards and reviewing workouts, recovery, and readiness inside the chat.201,325 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query a user's own Garmin Connect training, health, and recovery history through Garmin's official Personal API, backed by a local cache and built-in analysis tools.21117 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Strava running data, route planning, and weather information for intelligent running coaching.16MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to access and analyze intervals.icu training data including activities, fitness metrics (CTL/ATL/TSB), wellness stats, and calendar events. Supports natural language querying of athletic performance for training insights and workout planning.6-
- AlicenseBqualityDmaintenanceIntegrates with the Strava API to allow AI assistants to access fitness data including athlete profiles, activity history, and segment statistics. It enables users to query detailed performance metrics and explore geographic segment data through natural language commands.8125 npmMIT
TDQS
Scored across 24 tools
Most tools target distinct resources, but several physiological-metrics tools overlap heavily: matrix, matrix_summary, matrix_history, performance_profile, athlete_lab, pillar_deep_dive, and physio_tests all expose related profile/benchmark data. Descriptions help, but an agent could plausibly choose the wrong view when asked for 'performance metrics'.
Every tool follows the same get_enduraw_<snake_case_noun> pattern. The convention is predictable and consistent across all 24 tools.
24 tools is at the upper edge for a single server and feels heavy, especially with multiple matrix/performance variants. The broad analytics domain justifies many tools, but some consolidation would reduce surface area.
Coverage is strong for a read-only running-analytics domain: profile, activities, analysis, physiological pillars, races, course profiles, GPX, form/fatigue, and quotas are all represented. Minor gaps exist around write operations such as creating or editing pacing plans, but core retrieval workflows are covered.