Skip to main content
Glama
Sign In

JustGains

by com.justgains
OverviewDiscussionsAdmin

Server Details

Save workouts, read training history and progress, search exercises, and log food in JustGains.

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
18.1% over 22 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
JustGains/justgains-connector
GitHub Stars
0
Server Listing
justgains

TDQS

B3.4/5.0

Scored across 25 tools

Disambiguation3/5

Most tools have distinct resource+action targets, but the analytics cluster overlaps: get_my_workout_logs vs get_workout_history both return recorded workouts, and get_progress, summarize_my_week, and analyze_my_consistency all surface training aggregates over a window. create_workout vs generate_workout is also a subtle boundary that descriptions only partially resolve.

Naming Consistency4/5

Nearly all names follow a snake_case verb_noun pattern (create_workout, search_exercises, log_my_weight). The main deviation is the inconsistent use of the 'my' prefix—get_my_workout_logs carries it while the equally user-scoped get_workout_history and get_workout_program do not—plus one outlier verb (show_workout).

Tool Count3/5

At 25 tools this is heavy, sitting right at the top of the acceptable range for a multi-domain fitness app covering workouts, programs, exercises, nutrition, routes, and analytics. Several near-duplicate analytics/log tools feel like they could be consolidated rather than each earning a distinct slot.

Completeness4/5

Coverage is broad: workouts (create/generate/update/get), programs (create/get/search/enroll), exercises (search/details/history), nutrition (diary/log/remove/search), bodyweight (log/history), and routes. Gaps include no delete_workout or program-deletion operation and no profile-update tool, but core workflows are workable.

Tool Schema Changelog

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

  1. 3 tool updates
    • Changedanalyze_my_consistency1 field changed
      • changedInput schema / properties / endDate / description
        Previous value: -"Optional ISO-8601 anchor date, the window ends here instead of today. Use for retrospective consistency like 'how consistent was I in 2024'."New value: +"Optional ISO-8601 date at the end of the analysis window."
    • Changedget_my_exercise_history1 field changed
      • changedInput schema / properties / exerciseCode / description
        Previous value: -"Uppercase exercise code, e.g. 'BARBELL-BENCH-PRESS'. Use search_exercises if unsure."New value: +"Uppercase exercise code, for example BARBELL-BENCH-PRESS."
    • Changedsummarize_my_week1 field changed
      • changedInput schema / properties / endDate / description
        Previous value: -"Optional ISO-8601 anchor date, the window ends at this date instead of now. Use for retrospective summaries like 'how was my week ending Mar 30, 2024'."New value: +"Optional ISO-8601 date at the end of the summary window."
  2. 25 tool updates
    • First observedanalyze_my_consistency
    • First observedcreate_route
    • First observedcreate_workout
    • First observedcreate_workout_program
    • First observedgenerate_workout
    • First observedget_exercise_details
    • First observedget_my_exercise_history
    • First observedget_my_food_diary
    • First observedget_my_profile
    • First observedget_my_top_exercises
    • First observedget_my_weight_history
    • First observedget_my_workout_logs
    • First observedget_progress
    • First observedget_workout_history
    • First observedget_workout_program
    • First observedlog_my_food
    • First observedlog_my_weight
    • First observedremove_my_food
    • First observedsearch_exercises
    • First observedsearch_foods
    • First observedsearch_workout_programs
    • First observedset_my_program_engagement
    • First observedshow_workout
    • First observedsummarize_my_week
    • First observedupdate_workout

Related MCP Connectors

Related MCP Servers

  • trainheroic-mcp

    IBazylchuk
    A
    license
    C
    quality
    A
    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

  • MCP Logger

    JohnZolton
    F
    license
    B
    quality
    D
    maintenance
    A personal fitness tracking server that enables logging and querying workouts, nutrition, and body metrics through a local SQLite database. Integrates with OpenNutrition MCP for food logging and supports exercise history tracking for workout progression.
    17
    -

  • gym

    SklyerX
    A
    license
    Not graded
    quality
    B
    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

  • fitness-mcp

    wbratz
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables conversational logging and retrieval of workouts, sets, weigh-ins, meals, goals, plans, and progress photos through MCP-capable AI clients, with authenticated per-user storage and export/query capabilities.
    ISC
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources