What it returns

Field	Meaning
query	Case-insensitive substring of the exercise title, e.g. 'press'.
muscle_group	Filter on primary muscle group, e.g. 'chest', 'quadriceps', 'lats'.
custom_only	Only the user's own custom exercises. Defaults to false.
limit	Maximum rows to return. Defaults to 50.

Parameters

Name	Type	Description
`query`	`string`	Case-insensitive substring of the exercise title, e.g. 'press'.
`muscle_group`	`string`	Filter on primary muscle group, e.g. 'chest', 'quadriceps', 'lats'.
`custom_only`	`boolean`	Only the user's own custom exercises. Defaults to false.
`limit`	`integer`	Maximum rows to return. Defaults to 50.

Pass either days or an explicit start/end pair. start wins if both are given.

Output

A markdown table rather than JSON — roughly a third of the tokens, and models reason over rows more reliably than nested objects.

Notes and gotchas

Requires a connected Hevy account. Connect it from your dashboard — no developer account needed.
Read-only: this tool cannot change anything in your account.

Call it directly

The endpoint is plain JSON-RPC, so you can test without any client:

curl

curl -s https://fitnesspeak.app/mcp \
  -H "Authorization: Bearer fp_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "hevy_exercise_templates",
         "arguments": {}
       }
     }'

Tool description the model sees

Search the exercise catalogue available on the account — built-in exercises plus the user's custom ones — with muscle group, equipment and template id. Call this to find the exact name or id of an exercise before asking for its history, or when the user asks what exercises exist for a muscle group.

Descriptions say when to call a tool, not just what it does — that trigger wording is what models actually route on.

`hevy_exercise_templates`