Hevy MCP
Related Servers
Alternatives to Hevy MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables interaction with the Hevy fitness tracking platform through their API. Supports managing workouts, routines, exercise templates, and webhook subscriptions for comprehensive fitness data management.10 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables reading Hevy workout data and creating workout routines and logged workouts through Hevy's public API.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with the Hevy fitness tracking API for logging workouts, managing routines, and tracking fitness progress.34-
- AlicenseNot gradedqualityDmaintenanceExposes the Hevy workout API to Claude, enabling users to manage workouts, routines, exercise templates, body measurements, and user info via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceConnects 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
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
TDQS
Scored across 9 tools
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.
All tool names follow a consistent snake_case verb_noun pattern (list_workouts, get_workout, create_routine, etc.). No deviations or mixed conventions.
Nine tools is well-scoped for a fitness-domain MCP server. Each tool serves a clear purpose without redundancy or bloat.
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.