Skip to main content
Claude Desktop supports stdio MCP servers through an mcpServers configuration block. Add the hevy entry to your Claude Desktop config file, save it, restart the app, and Claude gains access to all 25 Hevy MCP tools in every conversation.
npx requires Node.js 20 or newer. Run node --version in a terminal to confirm before proceeding.

​
Using npx (local stdio)

The local stdio approach runs hevy-mcp as a child process on your machine. Claude Desktop manages the process lifetime automatically; you do not need to start or stop it manually.
1

Open your Claude Desktop config file

The configuration file location depends on your operating system:
Open it in any text editor. If the file does not exist yet, create it.
2

Add the hevy-mcp server entry

Merge the following mcpServers block into your config. If the file is empty, paste the entire object; if it already contains other servers, add the hevy key alongside them.
Replace your-hevy-api-key with the key from your Hevy app settings.
3

Save and restart Claude Desktop

Save the config file, then fully quit and reopen Claude Desktop. The MCP server is registered at startup; changes to the config file take effect only after a restart.
Restart Claude Desktop after every change to claude_desktop_config.json. The app reads the file once at launch and does not watch it for live changes.

​
Using the hosted endpoint

The hosted Cloudflare Worker at https://hevy.chrisdoc.dev/mcp requires no local Node.js installation. There are two ways to connect Claude to it.
Claude.ai (the web app) supports adding remote MCP servers through its Integrations settings. The hosted endpoint implements a full OAuth 2.1 flow with PKCE so Claude.ai can authenticate without you manually managing a bearer token.
  1. Open Claude.ai → Settings → Integrations → Add custom connector.
  2. Enter https://hevy.chrisdoc.dev/mcp as the server URL.
  3. Complete the browser authorization page that appears — paste your Hevy API key when prompted.
See the Hosted Endpoint page for a full walkthrough of the OAuth discovery and PKCE exchange flow.

​
Verify the connection

After restarting Claude Desktop, start a new conversation and ask:
Which Hevy account is connected?
Claude will call the get-user-info tool and respond with your Hevy display name and profile URL. If it responds without invoking a tool, the server is not connected — double-check the config file path and JSON syntax, then restart again.
You can also ask “What tools do you have available?” to see the full list of 25 Hevy MCP tools Claude can use.

​
Next steps

Hosted Endpoint

Learn how the Cloudflare Worker handles authentication and the OAuth 2.1 layer for Claude.ai connectors.

Guided Prompts

Use server-provided MCP prompts to kick off multi-step workflows like training analysis and workout logging.

Tools Overview

Browse all 25 tools available to Claude once hevy-mcp is connected.

Troubleshooting

Steps to diagnose missing servers, authentication failures, and npx errors.