Skip to main content
Glama
borgels

mcp-server-hevy

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-hevy

No user-submitted related servers found.

    Related Servers

    • hevy-mcp

      antnsn
      A
      license
      B
      quality
      D
      maintenance
      MCP server for the Hevy workout tracker API that allows reading and writing workouts, routines, exercise templates, and body measurements.
      22
      11 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
      79,651 npm
      483
      MIT

    • 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.
      22 npm
      1
      MIT

    • Hevy MCP

      zachsai
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI clients to the Hevy workout tracking app, allowing users to manage routines and exercises. It enables reading workout history and logging new fitness sessions through simple natural language commands.
      -

    • super-hevy-mcp

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

      andywangyzfh
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects agents and other MCP hosts directly to the official Hevy Public API for reading workouts, routines, exercise templates and history, routine folders, body measurements, and account information. Writes stay gated behind a server-level opt-in plus per-call confirmation, with credentials kept local via Keychain, an environment variable, or a key file.
      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/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: account management (connect/status/disconnect), workouts (list/single/count/events), routines (list/single/folders), exercise templates (search/get), plus dedicated tools for history, user info, and body measurements. No tools appear to overlap or cause confusion.

    Naming Consistency5/5

    All tools use the consistent hevy_ prefix and snake_case, with the vast majority following a verb_noun pattern (get_workouts, search_exercise_templates). Even the exceptions (connect, status, disconnect) are clear and fit the overall style without mixing conventions.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 well-scoped range, but each tool serves a distinct purpose in covering Hevy's account, workout, routine, and template data. The count is still reasonable and not bloated.

    Completeness2/5

    The tool set has significant gaps: it references hevy_update_routine (which is missing) and mentions creating workouts/routines via template IDs, but offers no create or update tools for workouts or routines. This leaves critical actions unavailable and creates a dead end for agents.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources