Hosted/gateway-ready Hevy fitness MCP: workouts, routines, templates.
{
"HEVY_API_KEY": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-rwestergren-hevy-mcp-remote": {
"url": "https://io-github-rwestergren-hevy-mcp-remote.example.com"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Hevy MCP (Remote) is an MCP server for Hosted/gateway-ready Hevy fitness MCP: workouts, routines, templates.. It supports HTTP transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
Hevy MCP (Remote) uses HTTP transport. Use the package or command config in Install.
Hevy MCP (Remote) inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Hevy MCP (Remote) is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/rwestergren/hevy-mcp:0.1.6streamable-http | oci | Not captured | Env: HEVY_API_KEY required secret |