Skip to main content
Glama
smart-gym-mcp
by sla1k

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SMARTGYM_DB_PATHNoDatabase locationSmartGym's container path
SMARTGYM_BACKUP_DIRNoPre-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 of routines) 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
smartgym_healthA

Check the credentials file, the SmartGym server, and the installed app version.

ok=true means the server answered with your account data. `problem` explains
what to fix otherwise (e.g. create the credentials file). `data_as_of` is the server's
last-modified time of the account data, in local time with its UTC offset — older than
the last workout on the iPhone means the app hasn't synced yet. `warning` appears when the installed SmartGym version
differs from the one the MCP was verified against.
smartgym_list_routinesA

List routines: id, name, days, and exercise counts per section (warm-up/main/cool-down).

Archived routines are listed only with include_archived=true. Use the id (or the
name) in the other tools.
smartgym_get_routineA

Get a routine split into warmup, main and cooldown sections.

Each exercise shows its exercise_id (what the edit tools take), rest, note, planned
template sets, and up to `history_depth` recent sessions (reps + weight_kg) with the
latest session's top set and total volume.
smartgym_get_workout_historyA

List past workouts (newest first) with duration, calories and heart rate.

Defaults to the last 7 days (or 14/30 via `days`); explicit `date_from` / `date_to`
(inclusive, local time) override it. Optional `routine` filter (name or id).
Paginated: total, has_more, next_offset.
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.

Each routine: name (must not match an active routine), goal (required free text, e.g.
"Strength" — the app can't save a routine without one), optional days/note, and three
ordered sections — `warmup` (optional), `exercises` (= main, required), `cooldown`
(optional). Each exercise: catalog name or id, optional rest_seconds, note and template
sets. Validation is all-or-nothing; dry_run=false creates the routines and verifies them
on the server.
smartgym_update_routineA

Edit a routine's name, days, goal or note (only the fields you pass; "" or, for days, [] clears).

The goal can be changed but not cleared (the app can't save a routine without one).
A new name must not match another active routine. dry_run=false snapshots the
routine, sends the edit, and verifies it on the server.
smartgym_add_exerciseA

Add a catalog exercise (built-in or custom) to a routine section (warmup / main / cooldown).

`position` counts within the section (0 = first; omitted = last). Optional rest,
note and template sets.
smartgym_move_exerciseA

Move an exercise to another section (or to another position in its section).

`position` counts within the target section (0 = first; omitted = last).
smartgym_remove_exerciseB

Remove an exercise from its routine (logged history is kept).

smartgym_reorder_routineA

Reorder exercises inside sections.

Each list you pass must hold exactly that section's current exercise_ids, in the new
order; omitted sections stay as they are. To change an exercise's section use
smartgym_move_exercise.
smartgym_update_exerciseC

Change an exercise's rest time, note ("" clears) or template sets.

`sets` is the FULL planned list [{reps, weight_kg}] — sets beyond it are removed,
extra ones added.
smartgym_apply_routineB

Rewrite a routine in one go (e.g. "week 2 of FB-A").

Each section you pass is the complete ordered list for that section: existing
exercises by exercise_id (optionally with new rest/note/sets), new ones by catalog
name (built-in or custom). An existing exercise listed under another section moves
there; one you leave out of a passed section is removed. Omitted sections stay as they
are.
smartgym_archive_routinesA

Archive routines (names or ids) on every device.

Reversible with smartgym_unarchive_routine.
smartgym_unarchive_routineC

Bring an archived routine back to the active list.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
catalog_exercisesRead-only exercise catalog from the SmartGym app bundle (Exercises.json).
catalog_equipmentRead-only equipment catalog from the SmartGym app bundle (Equipments.json).
catalog_categoriesRead-only category catalog from the SmartGym app bundle (Categories.json).

TDQS

A3.5/5.0

Scored across 15 tools

Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessLimited data