Skip to main content
Glama
jamoski3112

hevy-mcp

by jamoski3112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hevy-mcp

No user-submitted related servers found.

    Related Servers

    • hevy-mcp-server

      adamdavies1915
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with the Hevy fitness tracking API, allowing users to log workouts, manage routines, browse exercises, and track fitness progress through natural language.
      14 npm
      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.
      14 npm
      MIT

    • Hevy MCP Server

      jcjiron
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables interaction with the Hevy fitness tracking platform through their API. Supports managing workouts, routines, exercise templates, and webhook subscriptions for comprehensive fitness data management.
      88 npm
      ISC

    • hevy-mcp

      isaacfink
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the Hevy workout API to Claude, enabling users to manage workouts, routines, exercise templates, body measurements, and user info via natural language.
      79,651 npm
      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.1/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool clearly targets a distinct resource and action, such as workouts, routines, routine folders, and exercise templates. List/detail operations are separated with explicit singular naming (e.g., get_workouts vs get_single_workout), and no two tools appear to serve the same purpose.

    Naming Consistency4/5

    All tool names use snake_case and follow a verb_noun pattern (get_, create_, update_, delete_). Minor deviations exist with get_single_workout instead of get_workout and get_workout_count as a compound noun, but overall the naming is predictable and consistent.

    Tool Count4/5

    With 23 tools, the server feels slightly heavy, but the count is justified by covering four distinct resource types (workouts, routines, routine folders, exercise templates), each with appropriate CRUD operations. A few utilities like get_workout_count and get_workout_events add value without bloating the set excessively.

    Completeness3/5

    The server covers most core workflows: full CRUD for workouts, routines, and routine folders, plus listing, retrieving, creating, and deleting exercise templates. However, there is no update_exercise_template, which is a notable gap since creating and deleting without updating forces a delete/recreate pattern for adjustments.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources