hevy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEVY_API_KEY | Yes | Your personal Hevy API Key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workoutsA | Get a paginated list of workouts |
| get_workout_countA | Get the total number of workouts on the account |
| get_single_workoutA | Get a single workout’s complete details by the workoutId |
| delete_workoutA | Delete a workout by its workoutId |
| get_workout_eventsB | Retrieve a paged list of workout events (updates or deletes) since a given date |
| get_routinesC | Get a paginated list of routines |
| get_single_routineB | Get a routine by its Id |
| delete_routineB | Delete a routine by its routineId |
| get_routine_foldersC | Get a paginated list of routine folders |
| create_routine_folderB | Create a new routine folder |
| update_routine_folderC | Update an existing routine folder |
| delete_routine_folderB | Delete a routine folder by its folderId |
| get_exercise_templatesA | Get a paginated list of exercise templates |
| get_single_exercise_templateB | Get a single exercise template by id |
| delete_exercise_templateA | Delete a custom exercise template by its id |
| get_exercise_historyB | Get exercise history for a specific exercise template |
| create_workoutC | Create a new workout |
| update_workoutC | Update an existing workout |
| create_routineC | Create a new routine |
| update_routineC | Update an existing routine |
| create_exercise_templateC | Create a new custom exercise template |
| get_single_routine_folderB | Get a single routine folder by id |
| get_user_infoC | Get user info |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
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.
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.
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.
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.