> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chrisdoc.dev/hevy-mcp/llms.txt
> Use this file to discover all available pages before exploring further.

# Account tool — verify the connected Hevy user

> Reference for the get-user-info tool, which returns the authenticated Hevy account's user ID, display name, and public profile URL.

The `get-user-info` tool returns basic identity information for the Hevy account connected via the configured API key. It accepts no inputs and reports only the account associated with the configured credentials — there is no way to query a different user's profile through this tool.

## get-user-info

Returns the authenticated account's user ID, display name, and public profile URL.

**Kind:** Read-only

**Input parameters:** None.

**Returns:** An object containing three fields from the authenticated Hevy account:

| Field  | Type     | Description                                             |
| ------ | -------- | ------------------------------------------------------- |
| `id`   | `string` | The user's unique Hevy account ID.                      |
| `name` | `string` | The user's display name as shown on their Hevy profile. |
| `url`  | `string` | The user's public Hevy profile URL.                     |

<Tip>
  This is the lightest-weight tool to verify authentication. If `get-user-info` returns data, your API key is valid and the connection to the Hevy API is working correctly.
</Tip>

***

## Example response shape

```json theme={null}
{
  "id": "user_abc123",
  "name": "Jane Lifter",
  "url": "https://hevy.com/user/janelifter"
}
```

All three fields are returned as strings when present. Any field may be absent if the Hevy account does not have that information set.

***

## When to use this

**Before write operations** — call `get-user-info` before performing any mutation (create or update) to confirm you are connected to the intended Hevy account. This is especially important when managing multiple API keys or when an assistant session has been idle.

**In automated workflows** — use `get-user-info` at the start of a workflow as a lightweight health check. A successful response confirms the API key is active, the account has Hevy PRO access, and the MCP server can reach the Hevy API.

**Debugging authentication failures** — if other tools return authorization errors, `get-user-info` is the fastest way to isolate whether the problem is the key itself or a tool-specific input error.

<Note>
  `get-user-info` accepts no inputs and always reports the single account associated with the configured API key. It cannot be used to look up other Hevy users.
</Note>