/hevy-workouts
Use when the user asks to inspect, summarize, plan, log, or update Hevy workouts, routines, exercises, or body measurements.
Claude Code
$ npx -y skills add chrisdoc/hevy-mcp --skill hevy-workouts --agent claude-code
Codex
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a codex -y
Cursor
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a cursor -y
Gemini CLI
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a gemini-cli -y
GitHub Copilot
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a github-copilot -y
OpenCode
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a opencode -y
Windsurf
$ npx skills add chrisdoc/hevy-mcp --skill hevy-workouts -a windsurf -y
SKILL.md
hevy-workouts.SKILL.mdname: hevy-workouts
description: Use when the user asks to inspect, summarize, plan, log, or update Hevy workouts, routines, exercises, or body measurements.
Hevy workout workflows
Use the Hevy MCP connector for the user's authenticated Hevy account.
MCP server connection
This plugin registers the remote MCP server as `hevy` through the repository's `.mcp.json` file:
{
"mcpServers": {
"hevy": {
"type": "http",
"url": "https://mcp.hevy-mcp.dev/mcp",
"oauth": true
}
}
}When the plugin is installed, connect or authorize the `hevy` server in Claude's connector settings. The authorization page asks the user for their Hevy API key. Never put an API key in this skill, plugin files, or a conversation. If the server is unavailable, ask the user to complete the connector authorization instead of attempting to start a different server.
Use the tools and resources exposed by the `hevy` server for Hevy requests. Do not call the Hevy API directly or invent an alternative authentication path.
Analysis and retrieval
- Prefer `get-training-summary` for a high-level trend across workouts and body measurements.
- Use focused list and detail tools when the user asks about a particular workout, routine, exercise, or date.
- State the date range and distinguish observations from recommendations.
- Cite the workout or measurement evidence used in a summary when practical.
Mutations
- Treat create and update tools as state-changing operations.
- Before changing Hevy data, summarize the proposed change and confirm it with the user unless the user has already given an unambiguous instruction to make that exact change.
- Never invent completed set results, workout times, body measurements, or other missing values. Ask the user for missing values.
- Explain that create operations can produce duplicates if retried and that update operations replace existing values.
Health context
Workout and body-measurement data is personal information. Describe trends without diagnosing medical conditions, and recommend a qualified professional for medical advice.
Read more
name: hevy-workouts description: Use when the user asks to inspect, summarize, plan, log, or update Hevy workouts, routines, exercises, or body measurements.
Hevy workout workflows
Use the Hevy MCP connector for the user's authenticated Hevy account.
MCP server connection
This plugin registers the remote MCP server as `hevy` through the repository's `.mcp.json` file:
{
"mcpServers": {
"hevy": {
"type": "http",
"url": "https://mcp.hevy-mcp.dev/mcp",
"oauth": true
}
}
}When the plugin is installed, connect or authorize the `hevy` server in Claude's connector settings. The authorization page asks the user for their Hevy API key. Never put an API key in this skill, plugin files, or a conversation. If the server is unavailable, ask the user to complete the connector authorization instead of attempting to start a different server.
Use the tools and resources exposed by the `hevy` server for Hevy requests. Do not call the Hevy API directly or invent an alternative authentication path.
Analysis and retrieval
- Prefer `get-training-summary` for a high-level trend across workouts and body measurements.
- Use focused list and detail tools when the user asks about a particular workout, routine, exercise, or date.
- State the date range and distinguish observations from recommendations.
- Cite the workout or measurement evidence used in a summary when practical.
Mutations
- Treat create and update tools as state-changing operations.
- Before changing Hevy data, summarize the proposed change and confirm it with the user unless the user has already given an unambiguous instruction to make that exact change.
- Never invent completed set results, workout times, body measurements, or other missing values. Ask the user for missing values.
- Explain that create operations can produce duplicates if retried and that update operations replace existing values.
Health context
Workout and body-measurement data is personal information. Describe trends without diagnosing medical conditions, and recommend a qualified professional for medical advice.
Talk to your Hevy workout data from Claude, Cursor, Codex, and other MCP clients. Connect to the hosted MCP · Use the Hevy CLI · Watch the 18-second demo · Explore all 23 tools · Documentation
Other skills on hevy-mcp.
More skills from other plugins.
paddleocr-doc-parsing
Use this skill to extract structured Markdown/JSON from PDFs and document images—tables with cell-level precision, formulas as…
13c-metabolic-flux
Estimates intracellular metabolic fluxes from steady-state carbon-13 isotope-tracing measurements using validated atom maps,…
Questions about hevy-workouts.
- Which coding agents can use hevy-workouts?
- hevy-workouts installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

