LABSCO SUMMARY

Last night's sleep and heart rate arrive in the conversation instead of in an app you have to go and open.

ultrahuman_metrics is the entire server, and it takes a date, so a week's comparison is one call per day and there is no range or aggregate to ask for. That narrowness is also the appeal: one variable pair configured once, and the day's biometrics are available wherever the client is. Nothing writes back to the account.

What it is

A single-tool client for the Ultrahuman API that returns a day's health and fitness metrics for the configured user.

What you get

Health and fitness metrics for a given date — heart rate, sleep, steps, temperature and other biometric measurements
Date as the only argument, since the user email comes from the environment

Requirements

An Ultrahuman account with API access, supplied as ULTRAHUMAN_AUTH_TOKEN and ULTRAHUMAN_USER_EMAIL. The email is fixed by that variable, so the server reports on one user.

Setup effort

One command plus a key — npx -y ultrahuman-mcp, then supply credentials

See installation options

USE CASES

01

Checking how last night actually went before the day starts

Ask for a date and get that day's heart rate, sleep, steps and temperature back in the conversation, with the account email already fixed by the environment.

ultrahuman_metrics

1 tool

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`ultrahuman_metrics`

Fetch health and fitness metrics from Ultrahuman API for a specific date. The user email is configured via environment variable, so you only need to specify the date to retrieve health data including heart rate, sleep, steps, temperature, and other biometric measurements.

BEFORE YOU INSTALL

What to know first

Tools you get

1 tool when we connected. The health data list (heart rate, HRV, sleep stages and more) is what ultrahuman_metrics returns for one date, not separate tools. It only reads.

Requires

npx on PATH
ULTRAHUMAN_AUTH_TOKEN in your environment
ULTRAHUMAN_USER_EMAIL in your environment

Where it runs

Both documented setups run the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the one tool definition that rides along on every turn

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y ultrahuman-mcp

MCP Clients

Claude Desktop — local build

CLAUDE DESKTOP — LOCAL BUILD · JSON

{
  "mcpServers": {
    "ultrahuman": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_PROJECT>/dist/main.js"
      ],
      "env": {
        "ULTRAHUMAN_AUTH_TOKEN": "<YOUR_ULTRAHUMAN_AUTH_TOKEN>",
        "ULTRAHUMAN_USER_EMAIL": "<YOUR_ULTRAHUMAN_USER_EMAIL>"
      }
    }
  }
}

Claude Desktop — npx

CLAUDE DESKTOP — NPX · JSON

{
  "mcpServers": {
    "ultrahuman": {
      "command": "npx",
      "args": [
        "-y",
        "ultrahuman-mcp"
      ],
      "env": {
        "ULTRAHUMAN_AUTH_TOKEN": "<YOUR_ULTRAHUMAN_AUTH_TOKEN>",
        "ULTRAHUMAN_USER_EMAIL": "<YOUR_ULTRAHUMAN_USER_EMAIL>"
      }
    }
  }
}

Ultrahuman