mcp server
Hevy MCP Server
MCP server for managing workouts, routines, and exercise data through the Hevy API
Description as published by the maintainer. Source
- version 3.2.1
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 387 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 25 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 3.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-17 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-17 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Wellness Project
— last commit 2026-08-04, shares fitness
63 tools for Apple Health, Fitbit, Oura & Health Connect data in Claude, ChatGPT, Grok & Mistral.
-
Withings Health Data
— last commit 2026-07-27, shares fitness
MCP server for Withings health data — sleep, activity, heart, and body metrics.
-
Fitness Tools
— last commit 2026-07-24, shares fitness
Deterministic fitness calculators — TDEE, adaptive TDEE, body fat, 1RM, macros — with consensus.
-
io.github.AshwanthramKL/whoop-mcp
— last commit 2026-07-13, shares fitness
Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
-
io.github.briangaoo/totem
— last commit 2026-07-26, shares fitness
Totem — talk to your wearables with AI. Today: full Whoop access (48 tools).
-
io.github.briangaoo/whoop-mcp
— last commit 2026-07-26, shares fitness
Full read + write access to your Whoop fitness data via the private iOS API. 48 tools.
-
MusclesWorked
— last commit 2026-02-17, shares fitness
Exercise-to-muscle mapping: 856 exercises, 65 muscles, workout analysis & alternatives.
-
io.github.davidmosiah/apple-health-mcp
— last commit 2026-08-05, shares fitness
Unofficial local-first MCP server for Apple Health export data.
-
io.github.davidmosiah/fitbitmcp
— last commit 2026-08-06, shares fitness
Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents.
-
io.github.davidmosiah/garminmcp
— last commit 2026-08-06, shares fitness
Privacy-first unofficial Garmin Connect MCP for AI health, sleep, activity & recovery agents.
These share tags the maintainers applied themselves, such as fitness. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: claude, codex, fitness, hevy, mcp, mcp-server, model-context-protocol, workout-planner, workout-tracker.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab