egym-mcp
Related Servers
Alternatives to egym-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access and analyze your Hevy workout data, including workout history, exercise progress, personal records, and routines.423 npm3MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access and modify a user's real GymTimer workout and nutrition data stored in private iCloud, allowing natural-language queries about training history and the creation of workout templates and meal plans.21MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to read Technogym mywellness training history, including workout sessions, per-exercise set data, per-second exercise analytics, and heart-rate traces.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and manage a user's Fitia account, including profile, Premium, food search, diary, meal suggestions, and preview-first writes that require confirmation before mutating data.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to design strength training workouts, push them to Garmin Connect and your watch, and read back completed sessions and exercise history.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Garmin Connect fitness and health data, including activities, heart rate, sleep, and device information.MIT
TDQS
Scored across 18 tools
Most tools target clearly distinct resources (workouts, strength, bio age, body composition, plans, notes). A few near-pairs exist — get_recent_workouts vs get_workouts, get_available_plans vs get_plan, get_body_composition vs get_body_metric_history — but descriptions explicitly delineate the boundaries (relative days vs date range, last-trained vs stored values, summary vs single-metric history).
Every tool follows a consistent verb_noun snake_case pattern (get_*, search_exercises, save_plan, delete_plan, read_training_notes, add_training_note). No mixed conventions or camelCase deviations in tool names.
18 tools is slightly above the ideal range but each covers a distinct slice of the fitness domain (workouts, strength, body metrics, plans, notes, coaching). Nothing appears redundant or padded, so the count is reasonable though on the heavier side.
Strong read coverage across all major domains plus plan lifecycle (list/get/save/delete) and notes (read/add). Minor gaps: training notes can only be added, not edited or deleted, and there is no workout logging or exercise-detail lookup beyond the catalogue search, but agents can work around these.