Skip to main content
Glama

Server Details

Manage strength workouts and track exercise progress. Requires a LiftTrack account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
LiftTrack

TDQS

A3.9/5.0

Scored across 24 tools

Disambiguation4/5

The set separates resources cleanly: workout templates/detail, activities/detail, programs/detail, schedule entries, exercise search, training maxes, settings, and help. The main boundary wrinkle is unschedule_workout, whose name suggests workouts only but also removes scheduled runs; search_exercises vs validate_exercise_names also requires reading descriptions to choose correctly. Descriptions generally make intended use clear.

Naming Consistency5/5

All tool names use snake_case verb_noun patterns such as create_workout, get_activity_detail, schedule_run, set_training_max, and validate_exercise_names. The only mismatch is semantic rather than stylistic: unschedule_workout also handles runs. The pattern is highly predictable.

Tool Count4/5

At 24 tools, the surface is heavy but largely justified by distinct areas: workout CRUD, scheduling, activities, programs, coaching summaries, settings, training maxes, and help. Some small read-only helpers such as get_folders, get_user_settings, and get_coach_profile could potentially be consolidated, but each still has a clear place.

Completeness4/5

Core workout lifecycle coverage is strong: create, update, delete, list, detail, validate exercise names, and schedule/unschedule entries. Gaps are mostly read-only surfaces: no update_coach_profile, no update_user_settings, no custom-exercise creation, and no program creation/start/pause tools. These are minor-to-moderate for a coaching MCP, but core training and scheduling workflows are covered.

Available Tools

24 tools
create_workoutAInspect

Create a workout template with exercises, sets, loads, rest modes, and optional supersets. Exercise names must be exact display names from the catalog or the user's custom exercises.

Each exercise: name, target (reps|time), load (weight|percent), working_rest_mode (timed|off|lap), working_rest_seconds (required when working_rest_mode is 'timed'; omit otherwise), optional warmup_sets[], optional warmup_rest_mode (required when warmup_sets is present; same allowed values as working_rest_mode), optional warmup_rest_seconds (required when warmup_rest_mode is 'timed'), working_sets[] (min 1), and an optional superset label. working_rest_mode 'off' means continue straight to the next set/exercise with no rest. 'lap' means the watch pauses until the user presses the lap button. The same rest setting applies between sets within the exercise and after the exercise's last set (the inter-exercise rest). Each set has reps (when target=reps) or seconds (when target=time), and weight (when load=weight) or percent (when load=percent), plus optional rpe. weight is in the user's units (0 = bodyweight). percent is the percentage of training max itself, e.g. 65 for 65%, not a computed weight. The server computes the weight from the user's training max, and the call fails with a clear error if the exercise has no training max set. superset is an optional short label (case-insensitive, max 16 chars). Exercises sharing a label run as one superset on the watch — at least two exercises must share a label, max 16 distinct labels per workout. Optional folder_name is an exact folder name; it places the workout in that folder, or creates the folder if no folder has that name. Optional warmup (workout) and wait_for_lap_after (per exercise) control the open warmup step at the start and the wait for a lap button press between exercises. Omitting them applies the user's workout settings; pass them only when the user asked for something different in this request. Steps the settings add count toward the 100 step limit; if they push the workout over it, the error says so and passing false to make it fit is allowed. The result reports what was applied.

Example with a two-exercise superset: {"name":"Push","exercises":[{"name":"Barbell Bench Press","target":"reps","load":"weight","working_rest_mode":"timed","working_rest_seconds":90,"working_sets":[{"reps":5,"weight":185}],"superset":"A"},{"name":"Cable Row","target":"reps","load":"weight","working_rest_mode":"lap","working_sets":[{"reps":8,"weight":80}],"superset":"A"}]}

Inputs: name (required), exercises (required), warmup, folder_name. Returns: name, warmup, set_count, workout_id, +4 more

delete_workoutA
DestructiveIdempotent
Inspect

Permanently delete a workout template. This cannot be undone. Deleting a workout also removes it from any schedules and from the user's Garmin device. App default workouts cannot be deleted.

Args: workout_name: Exact workout template name (case insensitive). folder_name: Optional folder name to disambiguate duplicate names. The value "My Workouts" identifies a workout not in any folder.

If several workouts share the name, the call fails and lists each match with its folder without deleting any of them.

Inputs: workout_name (required), folder_name. Returns: folder_name, workout_name

get_activitiesA
Read-onlyIdempotent
Inspect

Get a coaching overview of the user's completed training in a date range: strength sessions, runs, and rides, newest first. Each activity has an activity_id, kind, name, date, days_ago, and minutes. Strength adds exercise names, working set count, and primary muscles trained; runs and rides add distance, pace or speed, average heart rate, heart rate zone load, and hard minutes, in the user's units. totals summarizes every activity in the range by kind.

Args: start_date: Start of the range (YYYY-MM-DD). Defaults to 30 days before end_date. end_date: End of the range (YYYY-MM-DD). Defaults to today. kinds: Optional subset of strength, run, ride. Defaults to all. limit: Max activities listed (default 40, max 100). totals still cover the whole range.

Inputs: kinds, limit, end_date, start_date. Returns: range, totals, truncated, activities, +1 more

get_activity_detailA
Read-onlyIdempotent
Inspect

Get one completed activity in full by its activity_id. Strength returns every exercise with the sets performed and the sets prescribed, weights in the user's unit. Runs and rides return distance, time, pace or speed, elevation, heart rate with minutes in each of the user's zones, effort (zone load, hard and easy minutes, Garmin training effect, the user's RPE), every lap, and running dynamics or cycling power when recorded, in the user's units.

Args: activity_id: The activity's id from the activity overview.

Inputs: activity_id (required). Returns: kind, name, minutes, days_ago, +5 more

get_coach_profileA
Read-onlyIdempotent
Inspect

Get the user's saved Coach Profile: experience level, primary goal, training days per week, session length, weekly endurance hours, available equipment, liked and disliked exercises, and free text goals and limitations notes. Returns an empty object when the user has not set up a profile yet.

Inputs: no named parameters. Returns: goals_notes, primary_goal, days_per_week, training_split, +7 more

get_exercise_historyA
Read-onlyIdempotent
Inspect

Get performance history for a specific exercise across sessions. Shows per-session sets, volume, estimated 1RM, and heaviest set, plus trends over time. When present, local_date is the session's calendar date in the user's client-reported timezone; date is a UTC timestamp.

Inputs: exercise_name (required), limit. Returns: trend, sessions, exercise_display_name

get_foldersA
Read-onlyIdempotent
Inspect

List the user's workout folders with exact name and workout count.

Inputs: no named parameters. Returns: folders

get_help_articleA
Read-onlyIdempotent
Inspect

Read a complete LiftTrack Help Center article or FAQ by its identifier. Returns the full instructions or explanation and the source URL.

Inputs: article_id (required). Returns: article

get_program_detailA
Read-onlyIdempotent
Inspect

Get one saved program's complete compact plan. Returns every program week without pagination. Within each week, repeated uses of the same workout_id are grouped into one item with all assigned day labels in days. The same workout_id in multiple weeks means the same saved workout is reused.

Inputs: program_id (required). Returns: name, pause, weeks, status, +4 more

get_programsA
Read-onlyIdempotent
Inspect

List the user's saved programs at the same summary level as LiftTrack's program cards: name, status, total weeks, current week when running, and days per week. Status is not_started, active, paused, or complete. Internal program lifecycle ids are never returned.

Inputs: no named parameters. Returns: programs

get_scheduleA
Read-onlyIdempotent
Inspect

Get upcoming scheduled workouts, starting with today. The returned dates are plain calendar dates, exactly as scheduled. Each entry's type says who owns it: one_off (scheduled for a single date), routine (the user's weekly routine), program (a started program), or endurance (a run placed on that date, with its steps under endurance). endurance.garmin_status: waiting (not on Garmin yet: more than 6 days away, or no Garmin link), sending, synced (on the Garmin calendar), failed, or removed. Each entry has a schedule_id that names it when removing it; ids are for tool calls only, never show them to the user.

Args: days_ahead: How many days ahead to look (default 14, max 60).

Inputs: days_ahead. Returns: scheduled

get_training_maxesA
Read-onlyIdempotent
Inspect

Get training max (1RM estimate) values for exercises. Returns all training maxes, or filter by exercise name.

Args: exercise_name: Optional exercise display name to filter (e.g. 'Barbell Back Squat').

Inputs: exercise_name. Returns: training_maxes

get_user_settingsA
Read-onlyIdempotent
Inspect

Get the user's workout settings: unit preference (lbs/kg), weight rounding, and the defaults new workouts get for the warmup step and waiting for the lap button between exercises.

Inputs: no named parameters. Returns: units, weight_rounding, skip_last_rest_step, default_warmup_enabled, +1 more

get_weekly_training_statusA
Read-onlyIdempotent
Inspect

Get a coaching summary for one Monday-Sunday training week: workouts completed vs goal, calendar days left including today, strength/hypertrophy/endurance set counts, credited sets per muscle vs the user's four-week average, and trained or missing movement patterns.

Week boundaries and days_left use the client-reported timezone when available, otherwise the optional timezone argument, otherwise UTC. The response includes the resolved timezone in week.timezone.

Args: week_start: Optional Monday in YYYY-MM-DD format. Defaults to the current week in the resolved timezone. timezone: Optional IANA zone id (e.g. 'America/Denver'), used when the client reports no timezone.

Inputs: timezone, week_start. Returns: week, workouts, muscle_load, training_focus, +1 more

get_workout_detailA
Read-onlyIdempotent
Inspect

Get the full structured detail of a workout template: exercise display names, sets, loads, rest modes, supersets, RPE, and percentages of training max. Takes workout_id or exact workout_name; when both are given, the id is used if it matches. An id returns at most one workout; a name returns every matching workout, each carrying its folder. Returns an empty workouts array when no workout matches.

Inputs: workout_id, workout_name. Returns: workouts

get_workout_templatesA
Read-onlyIdempotent
Inspect

List workout templates as a high level summary: name, folder, and exercise count, plus total_count. Returns at most limit templates (default 50, max 200); total_count indicates when the list was truncated. Optional folder_name filters by folder. Does not include individual exercises or sets.

Inputs: limit, folder_name. Returns: templates, total_count

schedule_runAInspect

Put a run on one date of the user's calendar. Nothing is saved for reuse: to put a run on another date, call again with its date. It shows on that date in the LiftTrack app and, when the user's Garmin account is linked, reaches their Garmin calendar and watch within 7 days of the date (runs further ahead wait until then). To change a scheduled run, remove it and schedule the new version.

date: YYYY-MM-DD, from today through 120 days ahead. Each step: type "step", phase, exactly one of minutes, seconds, distance, until_lap_press, plus optional effort, optional heart_rate_zone or heart_rate (at most one), and optional note. Each repeat: type "repeat", times (2 or more), and steps; repeats do not nest. Every distance reads in the run's distance_unit. effort is what the step should feel like and is shown on the watch. Only heart_rate_zone or heart_rate make the watch alert. The usual zone for each effort when guiding by heart rate: walk 1, recovery 1, easy 2, steady 3, tempo 3-4, threshold 4, hard 5, sprint 5. Pace is not a target; a pace cue belongs in note as words. Returns the entry's schedule_id (for tool calls only; never show ids to the user), a one line summary of the run, and totals: timed minutes and total distance are separate, and open_steps counts steps that last until a lap press.

Example: {"date":"2026-11-12","name":"6 x 800","distance_unit":"km","steps":[{"type":"step","phase":"warmup","minutes":15,"effort":"easy"},{"type":"repeat","times":6,"steps":[{"type":"step","phase":"work","distance":0.8,"effort":"hard","heart_rate_zone":5},{"type":"step","phase":"recovery","distance":0.4,"effort":"recovery"}]},{"type":"step","phase":"cooldown","minutes":10,"effort":"easy"}]}

Inputs: date (required), name (required), steps (required), distance_unit (required), +1 more. Returns: date, name, totals, summary, +2 more

schedule_workoutA
Idempotent
Inspect

Schedule a saved workout template on one calendar date. The workout appears on that date in the LiftTrack app and, when the user's Garmin account is linked, on their Garmin calendar and watch. If the workout is already on that date (scheduled once, by the weekly routine, or by a program), nothing is added and the existing entry is reported.

Args: workout_name: Exact workout template name (case insensitive). date: YYYY-MM-DD, from today through 30 days ahead. workout_folder_name: Optional folder name to disambiguate duplicate names.

Inputs: date (required), workout_name (required), workout_folder_name. Returns: date, workout_name, existing_type, garmin_linked, +1 more

search_exercisesA
Read-onlyIdempotent
Inspect

Search the exercise catalog by name, muscle group, and/or equipment. Returns display name, muscles, and equipment, best matches first, max 20 results. Every exercise in a workout must come from this catalog or the user's custom exercises.

Args: query: Free text search against exercise name (e.g. 'bench press', 'romanian deadlift'). muscle_group: Filter to a primary muscle group. equipment: Filter to an equipment type.

Inputs: query, equipment, muscle_group. Returns: results

search_help_centerA
Read-onlyIdempotent
Inspect

Search LiftTrack's Help Center articles and FAQs for instructions, feature explanations, and troubleshooting. Returns relevant text passages with article titles and source URLs.

Inputs: query (required), limit. Returns: results

set_training_maxA
DestructiveIdempotent
Inspect

Set the training max for an exercise, creating it or updating an existing value. The training max is the estimated one rep max used to compute workout weights for percentage-based loads. Updating an existing training max recalculates the weight of every workout where the exercise uses percentage of training max.

Args: exercise_name: Exact exercise display name from the catalog or the user's custom exercises. training_max: The training max value, in the user's units (lb or kg per their settings).

Inputs: training_max (required), exercise_name (required). Returns: units, outcome, previous, training_max, +1 more

unschedule_workoutA
DestructiveIdempotent
Inspect

Remove one entry from the user's calendar by its schedule_id: a workout scheduled for a single date, or a run. It also leaves the user's Garmin calendar. Saved workout templates are not changed; a run is gone. Occurrences created by the weekly routine or a program are refused and can only be changed in the LiftTrack app. workout_name and date must be the entry's own, as the schedule lists them; a mismatch is refused. If the same workout stays on that date (from the weekly routine, a program, or another one off), the result reports what holds it in still_scheduled_by.

Args: schedule_id: The entry's id from the schedule. Never show it to the user. workout_name: The entry's workout name. date: YYYY-MM-DD of the entry, today or later. Past entries are kept as the user's training record.

Inputs: date (required), schedule_id (required), workout_name (required). Returns: date, kind, schedule_id, workout_name, +2 more

update_workoutA
DestructiveIdempotent
Inspect

Change an existing workout template. workout_name is the exact current name; optional workout_folder_name disambiguates duplicate names and does not change folder membership. Omitted fields keep their current values.

name renames the workout. exercises replaces the entire exercise list, including all exercises and sets to retain. Progression links are preserved for exercises that keep their name. Each exercise uses an exact catalog or custom exercise display name, target (reps|time), load (weight|percent), working sets, and rest configuration, with optional warmup sets, supersets, RPE, and notes. The input schema defines the fields and constraints. Notes appear on the watch in the workout step description.

warmup turns the open warmup step at the start on or off; omitted, it stays as it is. Per exercise wait_for_lap_after: omitted, an exercise that was already in the workout keeps its value and a newly added exercise gets the user's workout settings. Pass either only when the user asked to change it. The result reports the final warmup and wait_for_lap_count.

A rename-only request contains workout_name and name, plus workout_folder_name if needed; it does not require exercises.

Inputs: workout_name (required), name, warmup, exercises, +1 more. Returns: name, warmup, updated, set_count, +3 more

validate_exercise_namesA
Read-onlyIdempotent
Inspect

Check that exercise names exist in the exercise catalog or the user's custom exercises. Names must be exact display names (case-insensitive). Returns all_valid plus every invalid name with up to 3 close catalog matches as suggestions.

Inputs: names (required). Returns: invalid, all_valid

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Connects MCP clients to your gym training data so you can review weekly set volume, stall trends, session history and body measurements, and make previewed, backed-up edits to your workout plan. Includes fractional set counting and e1RM progress tracking.
      13
      56 PyPI
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables reading training history and planning complete workouts on a personal calendar, including exercises with videos, sets, reps, per-set weights, supersets, notes, and block instructions. It also supports searching the exercise library, copying or moving sessions, and retrieving performance stats, personal records, and feedback.
      29
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to a self-hosted workout tracker so they can look up routines and history, log or edit workouts, adjust routines, manage exercises, and record bodyweight with OAuth-based per-profile access.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables logging workouts, sets, routines, food, water, and macros through natural-language chat in any MCP client, with OAuth-based secure access and timezone-aware daily tracking.
      ISC
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources