hevy-mcp

Hevy MCP Server

Hevy PRO users can use hevy-mcp to manage training records through AI assistants such as Claude Desktop and Cursor. It supports reading, creating, and revising workouts and routines, browsing exercise templates, and creating routine folders.

Server facts

hevy-mcp

Project

Author
chrisdoc
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
516
Last commit
Data as of

Tags

  • Filesystem
  • fitness api
  • hevy mcp

Overview

Hevy training logs are available to connected AI assistants through hevy-mcp's workout tools. Assistants can browse sessions in newest-first order, inspect a workout's exercises and timing, retrieve the account's workout count, and create or revise entries. For clients keeping local records, an events query returns updates and deletions since a chosen date without requiring another download of the entire workout list. Workout edits can cover descriptions, session times, privacy settings, and exercise data.

Routine planning combines access to existing routines with creation and editing tools. A new routine can be assigned to a folder, while the routine update tool cannot change that assignment. Folder tools list existing folders, retrieve their details, and create new ones. Exercise templates provide another planning reference, with default and custom entries exposing exercise types and muscle groups; the server keeps templates cached in memory. Integration instructions cover Claude Desktop and Cursor. Running the Node.js server requires a Hevy API key available with PRO, and communication uses stdio rather than HTTP or SSE.

hevy-mcp setup notes

  • hevy-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers