返回 MCP 目录
public公开dns本地运行

Hevy连接器

一种模型上下文协议(MCP)服务器实现,该服务器与Hevy健身追踪应用程序及其API进行接口。此服务器允许人工智能助手通过Hevy API访问和管理锻炼数据、routine、锻炼模板等(需要PRO订阅)。

article

README

hevy-mcp: Model Context Protocol Server for Hevy Fitness API

License: MIT smithery badge

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).

Features

  • 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

Prerequisites

  • Node.js (v20 or higher)
  • npm or yarn
  • A Hevy API key

Installation

Installing via Smithery

To install hevy-mcp for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @chrisdoc/hevy-mcp --client claude

Manual Installation

# Clone the repository
git clone https://github.com/chrisdoc/hevy-mcp.git
cd hevy-mcp

# Install dependencies
npm install

# Create .env file from sample
cp .env.sample .env
# Edit .env and add your Hevy API key

Integration with Cursor

To use this MCP server with Cursor, you need to update your ~/.cursor/mcp.json file by adding the following configuration:

{
  "hevy-mcp-server": {
    "command": "npx",
    "args": ["-y", "hevy-mcp"],
    "env": {
      "HEVY_API_KEY": "your-api-key-here"
    }
  }
}

Make sure to replace your-api-key-here with your actual Hevy API key.

Configuration

Create a .env file in the project root with the following content:

HEVY_API_KEY=your_hevy_api_key_here

Replace your_hevy_api_key_here with your actual Hevy API key.

Usage

Development

npm run dev

This starts the MCP server in development mode with hot reloading.

Production

npm run build
npm start

Available MCP Tools

The server implements the following MCP tools:

Workout 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

Routine Tools

  • 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

Exercise Template Tools

  • get-exercise-templates: Fetch exercise templates
  • get-exercise-template: Get a template by ID

Routine Folder Tools

  • get-routine-folders: Fetch routine folders
  • create-routine-folder: Create a new folder
  • get-routine-folder: Get a folder by ID

Project Structure

hevy-mcp/
├── .env                   # Environment variables (API keys)
├── src/
│   ├── index.ts           # Main entry point
│   ├── tools/             # Directory for MCP tool implementations
│   │   ├── workouts.ts    # Workout-related tools
│   │   ├── routines.ts    # Routine-related tools
│   │   ├── templates.ts   # Exercise template tools
│   │   └── folders.ts     # Routine folder tools
│   ├── generated/         # API client (generated code)
│   │   ├── client/        # Kiota-generated client
│   └── utils/             # Helper utilities
│       ├── formatters.ts  # Data formatting helpers
│       └── validators.ts  # Input validation helpers
├── scripts/               # Build and utility scripts
└── tests/                 # Test suite

Development

Code Style

This project uses Biome for code formatting and linting:

npm run check

Generating API Client

The API client is generated from the OpenAPI specification using Kiota:

npm run export-specs
npm run build:client

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Acknowledgements

help

运行方式说明

cloud

托管运行

托管运行通常表示这个 MCP Server 由服务方环境承载,用户一般按页面提供的连接方式或授权流程接入,不需要在本地长期启动一个 MCP 进程

  1. 打开服务方连接页
  2. 完成授权或复制端点
  3. 在 MCP 客户端中连接
terminal

本地运行 / 其它方式

本地运行通常需要用户在自己的电脑或服务器上安装依赖,把 server_config 复制到 MCP 客户端,并按 env_schema 补齐环境变量、密钥或其它配置

  1. 复制 server_config
  2. 安装所需依赖
  3. 补齐环境变量后重启客户端