What Hevy data reaches Claude
Hevy is useful to an AI assistant because the direct connection preserves structured strength-training detail instead of flattening a workout into a generic activity. Exercises, completed sets, reps, weight, and available RPE can become queryable history.
That history can sit next to sleep, recovery, steps, and body data from other Wellness Project sources. Hevy itself does not supply those wearable signals, so connect a recovery or health source separately if you want the assistant to reason across both training and recovery.
Claude does not receive a bulk wearable export. It asks Wellness Project for the supported rows needed for the question, through the authorized remote MCP connection with sign-in authorization.
How to connect Hevy to Claude
Your setup screen may look different.
AI assistants change their settings and navigation frequently. Menu names and steps can vary by web, desktop, or mobile client, device and operating system, plan, account type, version, and staged rollout. Treat the instructions on this page as a current guide and look for the equivalent Apps, Connectors, Plugins, or MCP controls if your version differs.
Create a Hevy API key
Hevy limits API access to Hevy Pro. Create a personal API key in Hevy's developer/API settings.
Connect Hevy in Wellness Project
Open Settings → Devices → Hevy, paste the personal API key, and run the initial sync. The integration reads workout history directly from Hevy.
Check set-level detail
Open a recent workout in Wellness Project and confirm the exercise names, sets, reps, weight, and any available RPE you expect are present.
Add Wellness Project as a Claude connector
In claude.ai, open Settings → Connectors, add https://wellnessproject.ai/api/mcp as a custom remote MCP connection, then sign in and authorize your Wellness Project account.
Ask Claude about your real history
Start with a bounded date range and a concrete question. For example: "Which lifts increased in working weight over the last eight weeks?" The assistant can then request the relevant Wellness Project rows instead of reasoning from a screenshot or one-off export.
What to ask Claude once Hevy is connected
The useful prompts compare your own history over time. These examples are shaped around the data this source actually sends to Wellness Project.
- Which lifts increased in working weight over the last eight weeks?
- Compare weekly hard sets for my major muscle groups and show where volume has stalled.
- Which exercises show the clearest progression in reps or load since last month?
Limits of the Hevy → Wellness Project → Claude path
Hevy Pro is required because Hevy gates API access behind that plan.
The integration is for workout history. It does not turn Hevy into a source of sleep, HRV, or recovery metrics; use another connected source for those signals.
Claude is reading an authorized Wellness Project MCP connection, not a native Hevy integration supplied by Claude's developer.
Connect Hevy, then ask Claude.
Sync the supported history into Wellness Project, authorize Claude, and ask questions against your real trend instead of exporting files or pasting screenshots.
