The Hevy MCP server enables AI assistants to interact with the Hevy fitness tracking app API for comprehensive fitness data management:
Workout Management: Fetch, create, update, and track workouts with detailed exercise data
Routine Management: Access, create, update, and organize workout routines
Exercise Templates: Browse and retrieve both standard and custom exercise templates
Folder Organization: Create and manage folders to categorize routines effectively
Utilized for code formatting and linting in the development process of the MCP server.
Used for environment variable configuration to store the Hevy API key.
Used for version control of the MCP server codebase.
Hosts the repository for the MCP server codebase.
Provides tools for accessing and managing workout data, routines, exercise templates, and folders through the Hevy fitness app API, enabling workout tracking and fitness management capabilities.
Required as a runtime environment (v20 or higher) for running the MCP server.
Used as a package manager for installing and managing dependencies of the MCP server.
Provides badge for license information in the README.
Supported as an alternative package manager for installing and managing dependencies.
A Model Context Protocol (MCP) server implementation that interfaces with the Hevy fitness tracking app and its API. This server enables AI assistants to access and manage workout data, routines, exercise templates, and more through the Hevy API (requires PRO subscription).
Workout Management: Fetch, create, and update workouts
Routine Management: Access and manage workout routines
Exercise Templates: Browse available exercise templates
Folder Organization: Manage routine folders
Node.js (v20 or higher)
npm or yarn
A Hevy API key
To install hevy-mcp for Claude Desktop automatically via Smithery:
To use this MCP server with Cursor, you need to update your ~/.cursor/mcp.json file by adding the following configuration:
Make sure to replace your-api-key-here with your actual Hevy API key.
Create a .env file in the project root with the following content:
Replace your_hevy_api_key_here with your actual Hevy API key.
This starts the MCP server in development mode with hot reloading.
The server implements the following MCP tools:
get-workouts: Fetch and format workout data
get-workout: Get a single workout by ID
create-workout: Create a new workout
update-workout: Update an existing workout
get-workout-count: Get the total count of workouts
get-workout-events: Get workout update/delete events
get-routines: Fetch and format routine data
create-routine: Create a new routine
update-routine: Update an existing routine
get-routine: Get a single routine by ID
get-exercise-templates: Fetch exercise templates
get-exercise-template: Get a template by ID
get-routine-folders: Fetch routine folders
create-routine-folder: Create a new folder
get-routine-folder: Get a folder by ID
This project uses Biome for code formatting and linting:
The API client is generated from the OpenAPI specification using Kiota:
This project is licensed under the MIT License - see the LICENSE file for details.
Contributions are welcome! Please feel free to submit a Pull Request.
Model Context Protocol for the MCP SDK
Hevy for their fitness tracking platform and API
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
A Model Context Protocol (MCP) server implementation that interfaces with the Hevy fitness tracking app and its API. This server enables AI assistants to access and manage workout data, routines, exercise templates, and more through the Hevy API (requires PRO subscription).
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrisdoc/hevy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server