Skip to main content
Glama
antnsn

hevy-mcp

by antnsn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to hevy-mcp

No user-submitted related servers found.

    Related Servers

    • super-hevy-mcp

      stonelasley
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Hevy workout tracker that enables users to query training history, log workouts, and manage routines via natural language.
      MIT

    • hevy-mcp

      rwestergren
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Hevy fitness tracking app, enabling management of workouts, routines, exercise templates, folders, and webhooks through AI assistants.
      25
      4,761 npm
      MIT

    • hevy-mcp

      andreparmar
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that interfaces with the Hevy fitness tracking API, enabling AI assistants to manage workouts, routines, exercise templates, and more via natural language.
      26
      4,761 npm
      MIT

    • Hevy MCP

      chrisdoc
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server implementation that interfaces with the Hevy fitness tracking app and its API. This server enables AI assistants to access and manage workout data, routines, exercise templates, and more through the Hevy API (requires PRO subscription).
      23
      4,761 npm
      510
      MIT

    • mcp-server-hevy

      borgels
      A
      license
      B
      quality
      C
      maintenance
      Enables access to Hevy strength-training data—workouts, routines, exercise history, and progression—via an MCP server with per-user credential encryption and optional write support.
      16
      Apache 2.0

    • hevy-coach-mcp

      gCuadros
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Hevy that fetches live workout data and computes analytics like e1RM, PRs, volume, and consistency, while enabling writes for routines, folders, and body measurements without modifying workout history.
      54 npm
      1
      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 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose covering different resources (workouts, routines, folders, exercise templates, body measurements, user info) and actions (create, get, update, plus specialized queries like events and history). No two tools are ambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_workout, get_exercise_template, update_body_measurement). There are no deviations or mixed conventions.

    Tool Count4/5

    22 tools is on the high side but justified by the broad scope of fitness tracking (workouts, routines, exercises, measurements, account info, syncing). Each tool serves a distinct purpose, and the count is within a reasonable range for a comprehensive MCP server.

    Completeness2/5

    The set covers create, read, and update operations for most resources, but delete operations are entirely missing (no delete_workout, delete_routine, delete_body_measurement, etc.). This is a significant gap that would cause agent failures when cleanup or removal is needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources