garmin-mcp-triathlon
Related Servers
Alternatives to garmin-mcp-triathlon
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides read access to Garmin Connect health and training data (sleep, heart rate, stress, HRV, activities) and supports writes like creating workouts, editing activities, and exporting files.-
- FlicenseAqualityBmaintenanceEnables an AI assistant to read Garmin Connect sleep, health, activity, and training data, and to write structured multi-sport workouts, calendar schedules, and performance metrics back into Garmin Connect.241-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Garmin Connect activities, workouts, and workout templates for querying and creating workout plans.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans on Garmin Connect, syncing to the user's watch.1MIT
- AlicenseCqualityBmaintenanceEnables access to Garmin Connect fitness data through 39 fine-grained tools covering body, heart, sleep, stress, activity, steps, hydration, devices, nutrition, goals, and user profile.40MIT
- FlicenseBqualityDmaintenanceIntegrates with Garmin Connect to retrieve activity data, health metrics, and provide AI-powered training insights and personalized coaching recommendations based on your fitness activities and performance trends.14-
TDQS
Scored across 172 tools
With 172 tools there is heavy overlap: get_activities_fordate / get_activities_by_date / get_activities / count_activities, get_stats / get_user_summary / get_stats_and_body, and a large family of run-workout builders (create_run_workout vs create_run_easy_workout/tempo/long/intervals/hills/progression) that differ only by defaults. The very detailed descriptions and explicit 'use X instead' notes (e.g. summary vs full variants, the get_garmin_coach_workouts alias) mitigate much of the confusion, but several boundaries remain fuzzy.
Almost everything follows a snake_case verb_noun pattern (get_*, set_*, create_*, delete_*, upload_*, schedule_*, log_*, search_*), which is highly predictable. Minor deviations exist: get_activities_fordate lacks the underscore used in get_activities_by_date, singular/plural varies (get_personal_record vs get_race_predictions), and upsert_and_log uses a non-standard verb.
172 tools is far beyond any reasonable agent-facing surface and reflects extreme specialization, redundant aliases (schedule_workout/schedule_workouts/schedule_week, upload_workout/upload_workouts), and near-duplicate summary/full pairs. This is the extreme-mismatch end of the scale even for a broad platform like Garmin Connect.
Coverage is remarkably broad: activity read/update/delete/create, health and sleep metrics, nutrition CRUD plus logging, workout build/upload/schedule/unschedule/delete, courses, gear, challenges and rich training analytics. Only minor gaps remain (no workout edit, no true hydration delete, no update for scheduled entries), and several are documented platform limitations the agent can work around.