Skip to main content

​
Hevy HTTP MCP

An HTTP Model Context Protocol (MCP) server for the Hevy workout tracker API. This MCP server exposes all core Hevy API operations as MCP tools over HTTP transport, enabling any MCP-compatible client to connect remotely and interact with your workout data.
This project is inspired by @chrisdoc’s hevy-mcp, with a focus on HTTP transport instead of stdio.

​
What you can do

Hevy HTTP MCP enables you to:
  • Query workout history - Retrieve and analyze your past workouts with pagination support
  • Manage routines - Create, update, and organize workout routines programmatically
  • Access exercise templates - Browse and filter exercise templates from Hevy’s database
  • Track workout events - Monitor workout updates and deletions in real-time
  • Connect to AI chatbots - Integrate your workout data with AI assistants like Poke and Claude

​
Use cases

  • AI workout assistants - Let AI chatbots access your workout history to provide personalized training advice
  • Workout analytics - Build custom analytics tools that query your Hevy data
  • Automated routine management - Create tools to automatically generate and update workout routines
  • Integration platforms - Connect Hevy to other fitness tracking or productivity tools

​
Get started

Installation

Install dependencies and configure your environment

Quickstart

Get your MCP server running in 5 minutes

Configuration

Configure authentication and server settings

Available tools

Explore all available Hevy API tools

​
Tech stack

Hevy HTTP MCP is built with modern, performant technologies:
  • Elysia - Fast and type-safe web framework for Bun
  • elysia-mcp - MCP plugin for Elysia
  • ofetch - HTTP client with automatic retry and error handling
  • Bun - Fast JavaScript runtime with native TypeScript support

​
Requirements

You need a Hevy Pro account to access the Hevy API and obtain an API key.
Before you begin, ensure you have:
  • Bun v1.0 or higher installed
  • A Hevy Pro account with API access
  • An API key from Hevy settings

​
Architecture

The MCP endpoint runs as an HTTP server on http://localhost:3000/mcp by default. All requests are authenticated using API key bearer tokens before reaching any tool handler. Your Hevy API key is only sent server-side to api.hevyapp.com and is never exposed to MCP clients. 
MCP Client (Claude, Poke, etc.)
       ↓ (HTTP + Authorization header)
Hevy HTTP MCP Server
       ↓ (Hevy API key)
Hevy API (api.hevyapp.com)

Build docs developers (and LLMs) love

Get started for freeTalk to us