Hevy integration for ChatGPT and Claude
Yes. Hevy can connect to ChatGPT or Claude over MCP through AIPx's adapter for the official Hevy API. A Hevy Pro subscription and vendor API key are required separately; configure a read-focused agent to review workouts and progress without changing your training log.
What your agent can do with Hevy
Read workouts, routines, exercise templates, exercise history and body measurements. The Hevy specification lacks friendly operation IDs, so the table uses HTTP methods and paths rather than invented MCP names. The API also supports creates and updates: hide those operations for the read-only workflow described here.
| Tool | What it does | Access | Mode |
|---|---|---|---|
| GET /v1/workouts | List workouts | read | Allow |
| GET /v1/workouts/{workoutId} | Workout details | read | Allow |
| GET /v1/routines | Routines | read | Allow |
| GET /v1/exercise_templates | Exercises | read | Allow |
| GET /v1/exercise_history/{exerciseTemplateId} | Exercise history | read | Allow |
| GET /v1/body_measurements | Measurements | read | Allow |
| POST /v1/workouts | Create workout | write | Hide |
| PUT /v1/workouts/{workoutId} | Edit workout | write | Hide |
Source labels describe the checked connection. Live discovery and provider access determine availability; account-specific agent names may be normalized. Modes in this table are recommendations, not a change to upstream permissions.
Capability snapshot: 14 October 2026 · provider source
Connect Hevy to ChatGPT
A Hevy ChatGPT integration uses the AIPx agent endpoint for the configured workout tools.
Use custom MCP access in ChatGPT when your account and workspace permit it. Add the AIPx agent URL after storing the Hevy API key in AIPx, not in a chat prompt. ChatGPT’s connector eligibility is separate from both AIPx Free and Hevy Pro.
A useful workout review names the date range and exercise template. Ask for logged sets, repetitions and weights, then separate the recorded values from the agent’s calculations. Missing workouts or inconsistent exercise names should be reported rather than filled in from memory.
Connect Hevy to Claude
The Claude setup below uses the same agent endpoint. For progress analysis, keep workout and exercise-history reads on Allow and hide create or update operations. AIPx Free can carry the connection, but it does not provide a Hevy Pro subscription or an API key.
Hevy MCP server options
| Route | Credential ownership | Fit |
|---|---|---|
| Official Hevy API | Your Hevy Pro API key | Applications built directly against the provider |
| Community Hevy MCP | Your runtime and key | A separately maintained tool surface |
| AIPx Hevy adapter | Stored vendor key and generated API tools | Reuse with different agent policies |
The official API documentation defines supported endpoints and access requirements. Community options include yerden/hevy-mcp and diecoscai/hevy-mcp. Those servers may wrap requests differently; their tool names are not names promised by AIPx.
A direct API script can be a better fit for a fixed export. AIPx adds a service handling the key and training data, with agent reuse and per-tool controls in return.
Connect Hevy to Claude, Claude Code, Cursor or Codex
Obtain a Hevy API key from an eligible Hevy Pro account and store it in the Hevy connection. The vendor subscription requirement remains even on AIPx Free.
- Open the AIPx dashboard, choose Hevy under Integrations and complete its connection form or authorization.
- Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
- Copy the agent’s complete URL. The examples below use
AGENT_ID; replace it with the actual value from your dashboard.
An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Hevy; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.
Connect Claude to Hevy
In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Hevy is the only service you need.
Hevy MCP in Claude Code
claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_IDAuthorize via /mcp, then retrieve the last four logged Hevy workouts without edits. Check exercise templates before comparing lifts. Claude Code MCP setup explains server and login settings.
Hevy MCP in Cursor
Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:
{
"mcpServers": {
"aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
}
}Sign in from Cursor and use workout or exercise-history reads for the requested date range. Hide every create/update endpoint for this analyst. The Cursor MCP guide covers connection configuration.
Hevy MCP in Codex
codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp listCodex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Hevy credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.
Custom MCP access in ChatGPT can retrieve the Hevy data authorized through AIPx. Hevy Pro and an API key are still required separately. Consult ChatGPT MCP setup for the client’s current plan and workspace restrictions.
Scope Hevy per agent
For a workout analyst, enable workout, routine and exercise-history reads. Body measurements can remain hidden unless the analysis specifically needs them. Hide every create and update endpoint for this agent; the underlying API key can still have broader authority.
The table recommends Allow for selected reads, while general product writes default to Confirm. A dedicated read-only policy is narrower. Use MCP access control to keep the tool surface aligned with the job.
Use Hevy with WHOOP
WHOOP can supply recovery and sleep context while Hevy supplies logged workouts. Compare dates and trends, and say what the data cannot establish. Withings adds a separate measurement source. A planning agent can read Google Calendar without editing either health app.
Workout history and interpretation limits
Recorded sets describe what was logged, not necessarily every set completed. Exercise templates help distinguish similarly named lifts, and date filters keep the answer tied to the requested period. Ask the agent to disclose missing entries before comparing trends.
Use the output as a summary of logged data. It should not diagnose an injury or prescribe training from a single workout. Provider API limits and account access remain in force, and writes require a separately authorized decision rather than an inference that “improve my plan” means editing the record.
Browse all MCP integrations to choose another connection for this agent.
The Hevy connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.
What to ask your agent
Name the Hevy account and a bounded task. Ask for source identifiers and a proposed result before approving a change.
FAQ
Can I connect Hevy to ChatGPT?
Yes. Connect Hevy in AIPx, create an MCP agent and add its copied URL as a Claude custom connector when your account and workspace permit. Choose tools before using the connection.
Can I connect Hevy to Claude?
Run claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID with your actual agent endpoint, then use /mcp to authorize and inspect tools. See Claude Code MCP setup.
Do I need Hevy Pro?
AIPx Free includes 3 active connected accounts and 1 agent; Pro is $3/month. Hevy Pro and a vendor API key are required separately. Provider subscriptions, API charges and the AI client's own connector access are separate. See AIPx pricing.
Can I make the Hevy agent read-only?
Yes. Add separately authorized Hevy connections and choose each account's tools independently for the agent. One endpoint can include both; it does not merge accounts or synchronize provider data.
Can I compare Hevy workouts with WHOOP?
Hevy API creates and updates are available in the provider specification. Hide those operations for a read-only agent; the read-only recommendation is an AIPx policy, not an API-key scope claim.