mcp-server-hevy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEVY_AUDIT_LOG | No | Path to audit log file, empty to disable | |
| MCP_HTTP_TOKEN | No | Bearer token for the MCP HTTP transport | |
| HEVY_STORE_PATH | No | Path to the store file | /data/store.json |
| HEVY_TIMEOUT_MS | No | Timeout for HTTP requests in milliseconds | 30000 |
| HEVY_ENABLE_WRITES | No | Set to 'true' to enable write tools | false |
| HEVY_ENCRYPTION_KEY | Yes | AES-256-GCM key for the credential store (openssl rand -hex 32) | |
| HEVY_PUBLIC_BASE_URL | No | Public origin, used to build the enrollment link | |
| HEVY_TRUST_FORWARDED_USER | No | Set to 'true' to trust forwarded user headers |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hevy_search_capabilitiesC | Find the right Hevy tool. Use first. |
| hevy_connectA | Start linking YOUR Hevy account. Returns a one-time link to a form where you paste your Hevy API key — the key is never sent through this conversation. Get the key from hevy.com/settings?developer in a BROWSER (it is not in the mobile app) — it requires an active Hevy Pro subscription. |
| hevy_statusA | Whether your Hevy account is linked. |
| hevy_disconnectA | Remove your stored Hevy API key from this server. |
| hevy_get_workoutsA | Your logged workouts, newest first, with full exercise and set detail. Max 10 per page. |
| hevy_get_workoutC | One workout by id. |
| hevy_get_workout_countA | Total number of workouts you have logged. |
| hevy_get_workout_eventsA | Workouts updated or deleted since a timestamp — use for incremental sync rather than re-reading everything. |
| hevy_get_exercise_historyA | Every recorded set for one exercise template over time — the right tool for judging progression on a specific lift. |
| hevy_get_routinesB | Your saved routines (training templates). Max 10 per page. |
| hevy_get_routineA | One routine by id. Always fetch this before hevy_update_routine — updates replace the entire routine. |
| hevy_get_routine_foldersD | Your routine folders. |
| hevy_search_exercise_templatesA | Find exercise templates by name to get the exercise_template_id needed for creating workouts/routines. Hevy has no server-side search, so this pages through templates and filters locally. |
| hevy_get_exercise_templateC | One exercise template by id. |
| hevy_get_user_infoA | Your Hevy profile (id, name, profile URL). |
| hevy_get_body_measurementsA | Body measurements stored in Hevy. READ-ONLY here by design: Withings is the source of truth for body weight and composition, so this server deliberately does not write measurements and create a second competing record. |
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 16 tools
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.
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.
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.
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.