smart-gym-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMARTGYM_DB_PATH | No | Database location | SmartGym's container path |
| SMARTGYM_BACKUP_DIR | No | Pre-write backups directory | ~/.smartgym-mcp/backups |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
SmartGym routines, exercises and workout history, read from and written to the SmartGym server. This is the user's live training data: a write reaches every device.
Every write tool defaults to dry_run=true: it returns the plan (old -> new) and sends nothing. Run it that way first, show the user the plan, and repeat the call with dry_run=false only once they confirm it.
routine(and each entry ofroutines) is a routine name (case-insensitive, partial allowed) or its id from smartgym_list_routines; an ambiguous name is refused.exercise_id (and the ids in reorder/apply lists) comes from smartgym_get_routine.
New exercises are catalog names (built-in or the account's custom exercises, fuzzy-matched deterministically) or catalog ids.
Template sets are [{reps, weight_kg}], weight_kg 0.0 = bodyweight; omitted sets become one 1x10 set, flagged in the plan. Logged workout history is never changed.
When a write's outcome is unknown, re-read the routine before retrying it.
If calls fail on credentials, smartgym_health says what to fix.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| smartgym_healthA | Check the credentials file, the SmartGym server, and the installed app version. |
| smartgym_list_routinesA | List routines: id, name, days, and exercise counts per section (warm-up/main/cool-down). |
| smartgym_get_routineA | Get a routine split into warmup, main and cooldown sections. |
| smartgym_get_workout_historyA | List past workouts (newest first) with duration, calories and heart rate. |
| smartgym_get_equipmentA | List equipment (owned_only=true: only what you selected) plus dumbbell/kettlebell weights. |
| smartgym_create_programA | Create one or more routines (a program) on the SmartGym server — all devices get them. |
| smartgym_update_routineA | Edit a routine's name, days, goal or note (only the fields you pass; "" or, for days, [] clears). |
| smartgym_add_exerciseA | Add a catalog exercise (built-in or custom) to a routine section (warmup / main / cooldown). |
| smartgym_move_exerciseA | Move an exercise to another section (or to another position in its section). |
| smartgym_remove_exerciseB | Remove an exercise from its routine (logged history is kept). |
| smartgym_reorder_routineA | Reorder exercises inside sections. |
| smartgym_update_exerciseC | Change an exercise's rest time, note ("" clears) or template sets. |
| smartgym_apply_routineB | Rewrite a routine in one go (e.g. "week 2 of FB-A"). |
| smartgym_archive_routinesA | Archive routines (names or ids) on every device. |
| smartgym_unarchive_routineC | Bring an archived routine back to the active list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog_exercises | Read-only exercise catalog from the SmartGym app bundle (Exercises.json). |
| catalog_equipment | Read-only equipment catalog from the SmartGym app bundle (Equipments.json). |
| catalog_categories | Read-only category catalog from the SmartGym app bundle (Categories.json). |
TDQS
Scored across 15 tools
Most tools target distinct resource+action pairs, but the exercise-editing cluster overlaps heavily: smartgym_apply_routine is effectively a superset of add_exercise, remove_exercise, move_exercise and reorder_routine, and move vs reorder differ only subtly. Descriptions do explicitly cross-reference each other (e.g. reorder tells you to use move_exercise for section changes), which mitigates but does not eliminate the misselection risk.
All tools use a consistent snake_case smartgym_ verb_noun pattern, making the set highly predictable. Minor deviations: create_program creates routines (resource name differs from the rest of the tool set), and archive_routines is plural while unarchive_routine is singular.
15 tools sits at the upper edge of a well-scoped set but each operation corresponds to a real editing primitive in the fitness-routine domain (create, update, section edits, ordering, archiving). Given the redundant apply_routine covers several of the granular tools, the count could plausibly be trimmed, but it is not excessive.
The routine lifecycle is well covered: list/get, create, update metadata, archive/unarchive, full exercise CRUD within sections, and bulk rewrite. Gaps are minor and mostly read-only: no hard delete of a routine, no custom-exercise creation in the catalog, and workout history is list-only with no per-workout detail or logging.