personal-mcp
Provides integration with Hevy, a fitness tracking app, enabling tools for retrieving recent workouts, exercise lookup, and training volume summaries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@personal-mcp list my latest workouts from Hevy"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
personal-mcp
A personal MCP server for connecting your own API integrations and exposing them as tools/resources/prompts.
Initial Scope
Fitness domain
Hevy provider integration
Related MCP server: Hevy MCP Pro
Project Structure
personal-mcp/
├── .github/
│ └── copilot-instructions.md
├── src/
│ ├── core/
│ │ ├── server/
│ │ ├── config/
│ │ ├── types/
│ │ └── utils/
│ ├── domains/
│ │ └── fitness/
│ │ ├── providers/
│ │ │ └── hevy/
│ │ ├── services/
│ │ ├── tools/
│ │ ├── resources/
│ │ ├── prompts/
│ │ └── types/
│ └── index.ts
├── tests/
│ ├── core/
│ └── domains/
│ └── fitness/
├── .env.example
├── package.json
├── tsconfig.json
└── README.mdQuick Start
Install dependencies.
Copy
.env.exampleto.envand set your API key(s).Start in dev mode.
npm install
npm run devNext Steps
Implement Hevy API client methods.
Add MCP tools for recent workouts, exercise lookup, and training volume summaries.
Add domain-focused tests under
tests/domains/fitness.
Available Tools
2 toolshevy_recent_workoutsB
Return a placeholder list of recent Hevy workouts
Inputs: no named parameters.
hevy_statusB
Report whether Hevy API configuration is available
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools are clearly distinct: one reports configuration status, the other returns workout data. There is no overlap in their purposes or expected outputs.
Both tool names follow a consistent pattern: 'hevy_' prefix followed by a snake_case noun. This makes the naming predictable and easy to understand.
With only two tools, the server feels thin and borderline under-scoped. While each tool serves a purpose, a typical server for a domain like workouts would benefit from more coverage.
The tool set is significantly incomplete for a Hevy workout integration. It only provides a status check and a placeholder list, lacking any real workout retrieval, creation, update, or delete operations.
Maintenance
Related MCP Connectors
Your Garmin, Oura, WHOOP, Hevy and 35 more fitness apps, queryable from your own AI.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Connect Claude, Cursor or any MCP client to your GymUp training data.
Connect your health, fitness, nutrition, sleep, and wearable data to your AI assistant.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceExposes Garmin Connect data and workout management to AI agents, supporting tools, resources, and prompts for health data, workout creation, and coaching workflows.1-
- AlicenseBqualityDmaintenanceA production-ready MCP server for the Hevy fitness API that exposes 27 tools for reading, writing, and analyzing workout data, enabling LLM-driven personal trainer workflows.2710 npmMIT
- AlicenseBqualityDmaintenanceConnects Lelly.chat workspace with AI agents, offering tools for tasks, reminders, health tracking, CRM, knowledge base, finance, and spiritual journaling via MCP.31MIT
- AlicenseNot gradedqualityCmaintenanceExposes personal health data (recovery, sleep, strain, etc.) as MCP tools for AI agents to query and analyze.5MIT