DkwtMCP
Related Servers
Alternatives to DkwtMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA read-only MCP server that gives Claude Desktop access to your Garmin Connect data — daily health metrics, sleep, activities, training status, and body composition.6MIT
- AlicenseNot gradedqualityBmaintenanceMCP 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.19MIT
- AlicenseNot gradedqualityBmaintenanceA local, read-only MCP server that gives Claude access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.MIT
- AlicenseAqualityCmaintenanceMCP server that connects Garmin Connect to Claude Desktop, allowing users to query health and fitness data (sleep, workouts, heart rate, HRV, stress, Body Battery, etc.) in plain English and also log weight, hydration, and schedule workouts.25MIT
- AlicenseNot gradedqualityBmaintenanceA local, single-user, read-only MCP server that gives Claude Code access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.1MIT
- FlicenseNot gradedqualityCmaintenanceA local, read-only MCP server that allows Claude Desktop to access Garmin Connect data such as activities and recovery metrics, enabling AI-assisted running plan creation and adjustment.-
TDQS
Scored across 22 tools
Most tools target distinct metrics (readiness, sleep, HRV, zones, activities, workouts, body composition), but there is minor overlap between garmin_fitness_metrics and garmin_training_status (both include VO2max) and between fitness_weekly_summary and fitness_recovery_vs_training. Descriptions are detailed enough to guide selection.
Naming mixes prefixes 'garmin_' and 'fitness_' with inconsistent patterns: nouns ('garmin_sleep'), verb_noun ('garmin_get_activities'), and multi-word descriptors ('fitness_recovery_vs_training'). No uniform convention, but still readable.
22 tools is on the higher side for a single server, but each serves a distinct purpose within the fitness/health domain. The count is justifiable given the comprehensive coverage of data retrieval, analysis, and workout management.
The tool surface covers data retrieval, workout scheduling, and analysis, with CRUD for workouts. Minor gaps: no manual input tools for sleep or HRV, and activities are read-only. However, core training and recovery workflows are well-supported.