Hevy MCP
Connect your agent to the Hevy fitness API with typed tools so you can script workouts, routines, and account data for a fitness side project or personal automation.
Overview
Hevy MCP is an MCP server for the Build phase that integrates the Hevy fitness API with spec-generated schemas and dry-run-safe writes over stdio.
What is this MCP server?
- MCP bridge to the Hevy fitness API with OpenAPI-style spec-generated schemas
- Dry-run-safe write operations to reduce accidental production mutations during agent coding
- npm stdio package @diecoscai/hevy-mcp (v0.5.0) with GitHub source
- Positioned for easy MCP client setup for solo builders
- Named Hevy MCP in registry title for discoverability
- npm package @diecoscai/hevy-mcp version 0.5.0
- stdio transport per MCP registry manifest
- Repository github.com/diecoscai/hevy-mcp
What problem does it solve?
You want agent help building against Hevy but lack safe, well-typed tools and keep breaking requests or mutating live workout data by mistake.
Who is it for?
Indie hackers building Hevy-connected apps, coaches’ tooling, or personal gym automations inside MCP coding workflows.
Skip if: Non-Hevy fitness stacks, users without API access, or teams needing a hosted multi-tenant backend instead of a local MCP adapter.
What do I get? / Deliverables
Your agent calls schema-backed Hevy tools—with dry-run on writes—while you implement integrations and automations faster.
- Agent-accessible Hevy API tools with spec-generated request/response shapes
- Dry-run guarded write operations during development
- Faster iteration on workout and routine automation code
Recommended MCP Servers
Journey fit
Canonical shelf is Build → Integrations because the server wraps a third-party fitness API for product features rather than launch, growth, or ops tooling. Integrations fits spec-driven MCP tools that read and write Hevy resources while you implement app logic or automations.
How it compares
Hevy API integration MCP with dry-run writes, not a generic workout planning methodology skill.
Common Questions / FAQ
Who is Hevy MCP for?
Solo builders and developers who already use Hevy and want MCP agents to read and write fitness data through a typed, safer integration layer.
When should I use Hevy MCP?
Use it during Build when you are coding features or scripts that sync workouts, routines, or account data with Hevy via an agent.
How do I add Hevy MCP to my agent?
Install @diecoscai/hevy-mcp, configure stdio in your MCP client, provide Hevy API credentials per the GitHub README, and enable dry-run for write tools while iterating.