hevy-mcp
by chrisdoc
hevy-mcp is a Model Context Protocol (MCP) server that interfaces with the Hevy fitness tracking app API, enabling AI assistants to access and manage workout data. It allows for workout and routine management, exercise template browsing, and folder organization.
Last updated: N/A
What is hevy-mcp?
hevy-mcp is a Model Context Protocol (MCP) server implementation designed to interact with the Hevy fitness tracking app's API. It provides a standardized way for AI assistants and other applications to access and manipulate workout data, routines, exercise templates, and routine folders within a user's Hevy account.
How to use hevy-mcp?
To use hevy-mcp, you need to install it either via Smithery or manually. After installation, configure the server with your Hevy API key in a .env file. You can then run the server in development or production mode. For integration with tools like Cursor, update the corresponding configuration file with the server's command and environment variables.
Key features of hevy-mcp
Workout Management (fetch, create, update)
Routine Management (access and manage)
Exercise Templates (browse)
Folder Organization (manage routine folders)
Use cases of hevy-mcp
AI assistant integration for workout logging
Automated workout routine generation
Personalized exercise recommendations
Data-driven fitness insights
FAQ from hevy-mcp
What is the Model Context Protocol (MCP)?
What is the Model Context Protocol (MCP)?
MCP is a standard for enabling communication between AI models and external tools or services.
Do I need a Hevy PRO subscription to use this?
Do I need a Hevy PRO subscription to use this?
Yes, accessing the Hevy API requires a PRO subscription.
How do I get a Hevy API key?
How do I get a Hevy API key?
You can obtain a Hevy API key from your Hevy account settings after subscribing to Hevy PRO.
What Node.js version is required?
What Node.js version is required?
Node.js version 20 or higher is required.
How do I contribute to the project?
How do I contribute to the project?
Contributions are welcome! Please submit a Pull Request with your proposed changes.