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
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server for Garmin Connect integration. Access your activities, health data, training metrics, and more through Claude and other LLMs.2265MIT
- AlicenseNot gradedqualityCmaintenanceMCP server to interact with Garmin Connect, enabling retrieval of health, activity, and device data through natural language.65MIT
TDQS
Scored across 24 tools
Most tools target distinct metrics, but there is meaningful overlap among the health/recovery/snapshot tools: get_recovery, get_health_summary, get_full_snapshot, get_body_battery_range, get_hrv_history, get_sleep, and get_stress all overlap in scope. The descriptions clarify ranges versus snapshots, but an agent could still hesitate about which tool to call for broad questions like "how am I doing?"
All tool names use snake_case and a consistent verb_noun pattern, overwhelmingly with the get_ prefix. download_activity_file is a deliberate action-specific deviation rather than an inconsistency.
At 24 tools, this server sits in the heavy range for a single MCP server, even though the Garmin domain is broad. Most tools are purposeful, but the count is large enough that selection and maintenance become harder.
The surface covers activities, recovery, sleep, HRV, stress, body battery, body composition, SpO2, hydration, steps, fitness metrics, zones, records, and raw activity download. Minor gaps remain, such as structured workouts, device/gear data, and direct access to per-sample activity streams outside the FIT download, but core workflows are well covered.