Skip to main content
Glama
elkno

GymTimer MCP Server

by elkno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GymTimer MCP Server

No user-submitted related servers found.

    Related Servers

    • hevy-mcp

      Alexisb1988
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read, analyze, create, and update Hevy workout data, including workouts, routines, exercises, and body measurements, through the Model Context Protocol.
      4,761 npm
      MIT

    • Hevy Trainer MCP Server

      malikmobeen12
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants directly to Hevy workout data, enabling analysis of training volume, strength progression tracking, and web searches for fitness research.
      MIT

    • leap

      RedFoxxo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read, log, edit, and analyze workouts, routines, body weight, media, and personal records on a self-hosted openGym instance through its own HTTP API. Writes are scoped to requested changes with automatic backups and conflict detection, and tools are grouped into read, write, delete, and admin permission tiers.
      1
      MIT

    • Caliverse MCP

      somaticbits
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    Deploy Server
    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

    TDQS

    A3.9/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are mostly distinct by resource and action: templates, exercises, nutrition, history, and preferences are clearly separated. The only real overlap is update_workout_template vs update_workout_template_name, where the latter is a narrower subset, but the descriptions make the intended use clear.

    Naming Consistency4/5

    Tool names follow a consistent snake_case verb_noun pattern overall (get_, create_, update_, delete_). The main deviations are the use of 'save' for some creation/replacement tools and the more granular update_workout_template_name, but these are minor and still readable.

    Tool Count3/5

    With 21 tools, the server is on the heavy side and sits in the borderline range. The count is defensible given the breadth of workout, nutrition, and analytics features, but a few tools could be consolidated.

    Completeness3/5

    Exercise and workout template CRUD are well covered, and nutrition has full plan-level lifecycle coverage. However, periodization has only save_periodization_plan with no way to read, update, or delete cycles, and there is no workout logging tool, which are notable gaps in the domain surface.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources