Skip to main content
Glama
roshanrao21

Hevy MCP

by roshanrao21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Hevy MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      43 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.
      53,842 npm
      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

    • 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
    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.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (list/get workouts, list/get routines, search templates, get history, create/update routine, create workout). Descriptions explicitly clarify boundaries and usage constraints, leaving no overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_workouts, get_workout, create_routine, etc.). No deviations or mixed conventions.

    Tool Count5/5

    Nine tools is well-scoped for a fitness-domain MCP server. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    The surface covers core read operations for workouts, routines, and exercise history, plus create/update for routines and create for workouts. Minor gaps exist (no delete for routines/workouts, no update_workout, no get_exercise_template by ID), but these are workaroundable for most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources