MoveMate: Gym Workout Tracker
Server Details
Gym workout tracker and planner: plan, log and analyze training from your own sets and weights.
- 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
- MoveMate: Gym Workout Tracker
- Claude
- MoveMate: Gym Workout Tracker
TDQS
Scored across 20 tools
Most tools target a distinct resource+action, and the descriptions actively police the tricky boundaries (search_exercises vs show_exercises, get_workout vs get_workout_details, get_personal_records vs get_exercise_progression, create_custom_workout vs create_planned_workout). The weakest pairs are get_profile vs get_body_profile and the four analytics tools (recent_workouts / training_stats / personal_records / progression), which are separable only because the descriptions carry explicit 'use X not Y' rules.
Every name is snake_case verb_noun with a small, predictable verb set (create_, get_, list_, update_, delete_, search_, show_, log_). Resource nouns are reused consistently (custom_workout, planned_workout, exercise), so the name alone usually predicts the tool's scope.
20 tools is on the heavy side for one domain, and a few pairs exist mainly to split rendering from lookup (get_workout/get_workout_details, search_exercises/show_exercises) or to split profile data (get_profile/get_body_profile). Each is defensible individually, but the surface could likely be condensed to ~14-15 without losing capability.
Core lifecycle is strong for exercises, saved workouts and planned sessions (create/read/update/delete), but deletion is asymmetric: there is no delete_custom_workout, no delete_custom_exercise, and no way to remove or edit a workout already logged via log_completed_workouts, which is a real dead end if history is recorded wrong. Body profile and exercise/body-stats are read-only, so onboarding data cannot be corrected through the tools.
Publisher details
- Operator
- MoveMate Inc.
- Operator website
- https://movemate.app
- Vendor relationship
- First-party
- Documentation
- https://movemate.app/ai
- Privacy policy
- Not provided
- Trust center
- Unknown
- Restrictions
- None
Available Tools
20 toolscreate_custom_exerciseCreate custom exerciseAInspect
Adds a new exercise to the user's own library, for when search_exercises doesn't have what they're after — including conditioning work such as a run, skipping or sprints, via exercise_type. The returned exercise_id can then be used with search_exercises results in create_planned_workout — never invent an exercise_id. Not safe to retry: calling this again with the same name creates a separate duplicate exercise, not the same one — check search_exercises first if unsure whether it already exists.
Inputs: name (required), notes, equipment, muscle_group, +1 more. Returns: name, exercise_id, exercise_type, equipment_matched, +1 more
create_custom_workoutCreate saved workoutAInspect
Saves a new workout to the user's own workouts ("My workouts" in the app) without putting it on the calendar — a reusable routine such as "Chest day". To also schedule it, pass the returned workout_id to create_planned_workout; to put a one-off session on a date, use create_planned_workout with an exercise list instead. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Propose the workout and get the user's agreement before calling. Not safe to blindly retry, though an identical call within two minutes returns the workout already saved instead of a second copy. Supersets and circuits are set with the superset_group label on each exercise — see that field for the rule it requires. Each exercise is measured by its own exercise_type (from search_exercises) — send the targets that type accepts. Free accounts can save a limited number of workouts from chat; a refusal for that reason says so and must not be retried.
Inputs: title (required), exercises (required), notes. Returns: total, locale, warnings, workouts, +4 more
create_planned_workoutCreate planned workoutAInspect
Schedules a workout in the app on a chosen date, in one of two ways. To schedule a workout that already exists — one of the user's saved workouts or a library workout, found with list_workouts — pass its workout_id and no title, notes or exercises: the session links to that workout exactly as scheduling it in the app does, so no copy appears in the user's saved workouts, and later edits to that saved workout show up in this session too. To build a new session, omit workout_id and pass title and exercises. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Not safe to blindly retry: client_request_id makes retries safe — a repeat call with the same ID returns the existing workout instead of creating a duplicate. Supersets and circuits are set with the superset_group label on each exercise — see that field for the rule it requires. A workout can mix strength and conditioning freely: each exercise is measured by its own exercise_type (from search_exercises), so a run, a skipping round or a set of sprints sits in the same list as the lifts — send the targets that type accepts. Free accounts can hold a limited number of upcoming planned workouts; a refusal for that reason says so and must not be retried.
Inputs: scheduled_for (required), notes, title, reminder, +3 more. Returns: title, locale, web_url, warnings, +7 more
delete_planned_workoutDelete planned workoutADestructiveIdempotentInspect
Cancels a planned (not yet done) workout and takes it off the schedule. Only affects upcoming planned workouts — a workout already marked done or skipped cannot be removed from chat. Removes only the session: a saved workout it was scheduled from stays in the user's saved workouts. When the same workout is scheduled more than once, pass session_date to pick the session.
Inputs: workout_id (required), session_date. Returns: deleted, workout_id
get_body_profileGet body profileARead-onlyInspect
Body stats and training preferences the user entered in MoveMate (height, weight, age, gender, fitness level, activity level, goals, available equipment), whether MoveMate onboarding is complete, and the lifetime count of completed workouts. Use for program design or nutrition estimates that depend on these values.
Inputs: no named parameters. Returns: age, goals, gender, height_cm, +6 more
get_exercise_progressionGet exercise progressionARead-onlyInspect
Per-exercise trend over time — weight, reps, and estimated 1RM per workout. Returns a chart for one explicitly requested exercise. Call at most once and only when the user names a specific exercise. For broad PR or overall-progress requests, use get_personal_records and get_training_stats instead; never fan this tool out across PRs or exercises.
Inputs: period, exercise_id, exercise_name. Returns: trend, locale, period, points, +7 more
get_personal_recordsGet personal recordsARead-onlyInspect
The user's best set per exercise (by estimated 1RM), most impressive first. Returns the complete requested PR list in one call. Never call get_exercise_progression for every returned record; only use progression when the user explicitly names one exercise.
Inputs: limit, exercise_id. Returns: records
get_profileGet profileARead-onlyInspect
Returns the connected user's display name, timezone, and training frequency.
Inputs: no named parameters. Returns: timezone, display_name, member_since, workouts_per_week_avg
get_recent_workoutsGet recent workoutsARead-onlyInspect
What the user ACTUALLY did in past sessions, set by set — reps and weight of every completed set, total reps per exercise, and the planned targets they were working against. This is the tool for "how did I do?", for coaching progressive overload, and for anything about bodyweight work, where reps per set and total reps are the result and volume in kg is always 0. Narrow with exercise_name to get the same movement across its last few sessions.
Inputs: limit, workout_id, exercise_id, exercise_name. Returns: locale, workouts, candidates, filtered_by_exercise
get_training_statsGet training statsARead-onlyInspect
Answers "how am I doing" — totals, volume, weekday frequency, and streak over a rolling period. Returns one complete training-stats summary for one rolling period. Call exactly once per distinct requested period/offset window (for a 7-day/30-day comparison, exactly two calls: last_7d and last_30d). Never call once per day, workout, exercise, set, or muscle group, and never repeat an identical period/offset pair in the same answer.
Inputs: offset, period, muscle_group. Returns: locale, offset, period, streak, +10 more
get_workoutGet workoutARead-onlyInspect
Returns one specific MoveMate workout by its exact workout_id and renders the same workout card as list_workouts. Use this whenever the user asks to show, open, or display a particular workout already identified earlier in the conversation, especially one returned by create_planned_workout, update_planned_workout, list_planned_workouts, or list_workouts. Do not answer with only a text summary when a valid workout_id is available.
Inputs: workout_id (required). Returns: total, locale, workouts
get_workout_detailsGet workout detailsARead-onlyInspect
Returns a workout's full contents — every exercise with its exercise_id, exercise_type, sets and targets, rest, notes and superset grouping — in exactly the shape update_custom_workout, update_planned_workout and create_custom_workout accept. Call it before changing a workout's exercises: those tools replace the whole list, so start from this one, change what the user asked for, and send the rest back unchanged. Works for the user's saved workouts, library workouts and the workouts of scheduled sessions (workout_id from list_workouts, list_planned_workouts or an earlier write). To show the user a workout card instead, use get_workout.
Inputs: workout_id (required). Returns: type, notes, title, locale, +3 more
list_planned_workoutsList planned workoutsCRead-onlyInspect
What's coming up — so the model can answer that and avoid double-booking.
Inputs: to, from. Returns: planned_workouts
list_workoutsList workoutsARead-onlyInspect
Browses MoveMate's workout catalog — both the shared library and the user's own custom workouts, together by default. Use this to find an existing workout to schedule (pass its workout_id to create_planned_workout) rather than building one from scratch, to find one of the user's saved workouts to change (update_custom_workout, after reading it with get_workout_details), to browse by body focus ("give me a leg workout" — use category), or to look up one the user just opened in the app by its workout_id. Not the user's calendar (see list_planned_workouts) and not training history (see get_recent_workouts).
Inputs: type, limit, query, category, +1 more. Returns: total, locale, workouts
log_completed_workoutsLog completed workoutsAInspect
Records workouts the user has ALREADY FINISHED into their MoveMate history — "log yesterday's workout: bench 4x8 at 80 kg, squats 3x5 at 100", or a short history the user is moving over from notes or another app. Send whole sessions with the sets actually done, up to 20 workouts per call. Not a live tracker: if the user wants to log set by set while training, point them to the workout tracker in the MoveMate app (rest timer, weight suggestions) instead of calling this after every set. Dates: a workout from before the user joined MoveMate is history and may have any date; a workout from since they joined must be from today or the last 14 days. For a future date use create_planned_workout. At most 300 past workouts can be moved in through chat in total; for a longer history or an export file from another app (Hevy, Strong and others), tell the user about the workout import in the MoveMate app instead. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Each exercise is measured by its exercise_type (from search_exercises); send the fields that type uses: default = weight and reps (most strength work, and bodyweight work with reps such as pull-ups or hill sprints); time = duration only (planks, dead hangs, skipping); time_weight = duration and weight (weighted plank, farmer hold); distance_time = distance and duration (outdoor running, cycling or swimming, rowing machine, SkiErg — anything whose monitor shows distance rather than km/h); weight_distance = weight and distance (farmer walk, sled push); cardio_machine = speed in km/h, the machine level (incline or resistance) and duration — treadmill, stationary bike, stepmill; distance is derived from speed and time. Continuous cardio (cardio_machine, distance_time) is ONE set per session — a 20-minute treadmill walk is a single set of 1200 seconds, not three. If you had to guess any exercise, weight, rep count or date, read the workouts back and get the user's agreement before calling. Safe to retry: a workout already in the history (same date, start time and title) is not added twice. Free accounts can finish 3 workouts in total (in the app and here together); workouts from before they joined do not count. A refusal for that reason says so and must not be retried.
Inputs: workouts (required). Returns: failed, logged, app_url, history_added, +3 more
search_exercisesSearch exercisesARead-onlyInspect
Looks up exercises in MoveMate's library (including the user's own custom exercises) and returns their exercise_id and exercise_type. Renders nothing for the user — it is the lookup for building or editing a workout. The model must only compose workouts from exercises returned here — never invented ones. Resolve every exercise a workout needs in ONE call: pass all their names in queries rather than calling once per exercise. Each result carries an exercise_type saying how that movement is measured (reps, time, distance, or speed and level on a cardio machine) — it decides which target fields create_planned_workout will accept for it, so read it before writing sets. To show exercises to the user ("what can I do for chest?"), call show_exercises instead.
Inputs: limit, query, queries, equipment, +1 more. Returns: locale, exercises
show_exercisesShow exercisesARead-onlyInspect
Shows exercises from MoveMate's library (including the user's own custom exercises) to the user as a card grid with images, target muscles and their own history. Use it only when the user wants to see or browse exercises — "what are good chest exercises?", "show me dumbbell moves" — once per request. Not for looking up exercise IDs while building a workout: search_exercises does that without filling the chat. The cards already show names and muscles, so reply with a short comment or recommendation rather than listing them again. Results carry exercise_id and exercise_type like search_exercises, so a follow-up workout can use them directly.
Inputs: limit, query, equipment, muscle_group. Returns: locale, exercises
show_getting_startedShow getting startedARead-onlyIdempotentInspect
Shows a MoveMate quick-start card with first steps the user can tap: plan this week, a workout for today, or bring over past workouts. Tapping one sends it as the user's next message. Use it once when get_profile reports a new account and the user has no specific request yet, or when the user asks what they can do with MoveMate here. It changes nothing in the account.
Inputs: no named parameters. Returns: locale, actions, new_account
update_custom_workoutUpdate saved workoutADestructiveIdempotentInspect
Changes one of the user's own saved workouts ("My workouts" in the app) — rename it, change its note, or replace its exercise list — the same as editing it in the app. Every scheduled session that uses this workout shows the change too, including upcoming ones; the response says how many. Library workouts cannot be changed: to make a personal version, save one with create_custom_workout. Pass only the fields you want to change; anything omitted stays as-is. exercises, if given, replaces the whole list — to add an exercise, pass the existing ones plus the new one in the right position; to remove one, pass the list without it. ALWAYS read the current list with get_workout_details first and send it back with your change — never rebuild it from memory, or the exercises, sets and weights you leave out are lost. Confirm the change with the user before calling. Each exercise is measured by its own exercise_type — send the targets that type accepts.
Inputs: workout_id (required), notes, title, exercises. Returns: total, locale, warnings, workouts, +4 more
update_planned_workoutUpdate planned workoutADestructiveIdempotentInspect
Changes a workout that has not been done yet — reschedule it, rename it, or replace its exercise list. Works on an upcoming session and on one the app marked skipped because its time passed; rescheduling a skipped session makes it upcoming again. A finished workout cannot be changed. Pass only the fields you want to change; anything omitted stays as-is. exercises, if given, replaces the whole list — to add an exercise, pass the existing ones plus the new one; to remove one, pass the list without it. Read the current list with get_workout_details first; never rebuild it from memory. Because the list is replaced wholesale, any superset_group labels left out are removed too. A session's title, notes and exercises belong to the workout it uses: if that workout is one of the user's saved workouts, the change applies to it and to every other session using it, as editing it in the app does; if it is a MoveMate library workout, which cannot be changed, the user's sessions of it switch to their own edited copy. Rescheduling and reminders only ever affect the one session. When the same workout is scheduled more than once, pass session_date to pick the session. A workout can mix strength and conditioning freely: each exercise is measured by its own exercise_type (from search_exercises), so a run, a skipping round or a set of sprints sits in the same list as the lifts — send the targets that type accepts.
Inputs: workout_id (required), notes, title, reminder, +3 more. Returns: title, locale, web_url, warnings, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Workout log your AI fills in: sets from text or notebook photos, daily plans, history and records.
Strength training log: read your workouts, stats and gyms, and plan, log or edit sessions.
Gym log and calorie tracker: log meals, water, weight and fasts, review lifts, build programs.
Plan workouts, find exercises and gyms, log sessions and track progress with Gym Navigator.
Related MCP Servers
- AlicenseCqualityBmaintenanceEnables 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.29MIT
- AlicenseAqualityCmaintenanceConnects 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.1356 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to plan, build, and log calisthenics workouts in a user's own account, including searching exercises, managing custom workouts and plans, reading progress and coaching data, and logging completed sessions. Account mutations require explicit confirmation, and workouts can be displayed as interactive cards in the chat.MIT
- FlicenseAqualityDmaintenanceEnables workout logging, volume calculation, exercise database search with 1500+ exercises, and AI-powered workout plan generation with DynamoDB persistence.14-
Glama MCP Gateway
Add one secure layer between your agents and this server.