mcp-garmin-connect
Related Servers
Alternatives to mcp-garmin-connect
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that integrates Garmin Connect data with LLMs to provide personalized running analysis and training plans. It enables users to monitor performance metrics, manage training loads, and receive data-driven workout suggestions based on health indicators like VO2 Max and recovery status.435-
- FlicenseAqualityDmaintenanceMCP server that connects AI assistants to Garmin Connect health and fitness data, enabling natural language queries about workouts, sleep, heart rate, and more.29-
- AlicenseNot gradedqualityCmaintenanceMCP server that connects Garmin Connect data to Claude, enabling training analysis, recovery checks, and personalized plans based on real metrics like HRV, training load, and activities.21MIT
- AlicenseAqualityBmaintenanceAn 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.14Apache 2.0
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server for Garmin Connect integration. Access your activities, health data, training metrics, and more through Claude and other LLMs.2264MIT
- AlicenseNot gradedqualityCmaintenanceMCP server to interact with Garmin Connect, enabling retrieval of health, activity, and device data through natural language.64MIT
TDQS
Scored across 15 tools
Most tools target distinct data domains (sleep, stress, HRV, zones), but several aggregate tools overlap heavily: get_health_summary recombines get_recovery/get_sleep/get_stress, get_full_snapshot subsumes nearly everything, and get_running_summary vs get_monthly_running_stats vs get_recent_load blur the line on running/training aggregation. An agent could reasonably pick the wrong summary tool.
Every tool follows the same get_<noun> snake_case convention with no deviations. Predicable and easy to scan.
15 tools is well within a healthy range for a multi-domain fitness server, and each surface maps to a real Garmin data area. Slightly heavy on overlapping summary/snapshot tools, but not excessive.
Broad read coverage: activities, fitness, recovery, sleep, stress, RHR, zones, PRs, and running stats. As a read-only analytics server it is fairly complete, though there is no way to list workouts/planned activities or fetch raw timeseries detail beyond the summaries.