Skip to main content
Glama
RedFoxxo

leap

by RedFoxxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to leap

No user-submitted related servers found.

    Related Servers

    • opengym-conector

      derikkruger
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to plan, log, and analyze workouts conversationally through Claude or ChatGPT, with all changes recorded via the official openGym API and synced across their devices.
      AGPL 3.0

    • 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

    • hevy-mcp-server

      RyK57
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to read and write Hevy workout tracking data, including workouts, routines, exercise templates, per-exercise history, and body measurements through all 15 Hevy public API endpoints.
      7 npm
      MIT

    • GeniusFitness MCP

      PulsarInteractive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access and manage fitness programs, exercise catalog, workout resources, activity metrics, journaled plan edits, and change tracking through authenticated tools.
      0
      MIT

    • GymTimer MCP Server

      elkno
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to access and modify a user's real GymTimer workout and nutrition data stored in private iCloud, allowing natural-language queries about training history and the creation of workout templates and meal plans.
      21
      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

    B3.4/5.0

    Scored across 74 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, helped by very detailed descriptions (e.g. read_workouts vs read_workout, read_exercises vs read_exercise). The planning/scheduling cluster (write_schedule_mode, write_week_plan, write_day_plan, write_rotation, write_rotation_round, write_session_queue) has overlapping domain language and could still confuse an agent, though the descriptions explain each role.

    Naming Consistency5/5

    All tool names use consistent snake_case and a verb_noun pattern with shared read_/write_/delete_ prefixes, plus a clean admin_ namespace. read_me and admin_users are minor deviations but overall the naming is highly predictable.

    Tool Count1/5

    74 tools is far beyond the ideal 3–15 range and beyond even the 25+ heavy threshold; it reflects an extremely feature-rich server but creates a bloated surface. Each tool may earn its place, but the count alone is an extreme mismatch for agent usability.

    Completeness5/5

    The surface covers the full workout lifecycle (log, update, delete), routines, planning/rotation, body metrics, exercise catalogue, media, AI Coach, account, settings, and admin operations. With escape-hatch read_document/write_document for uncovered fields, there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources