get_hrvLABSCO SUMMARY
Correlations across sleep, activity and body metrics — the questions the Withings app does not answer.
The app shows each metric on its own screen; here every stream arrives in one conversation, so questions like how last week's sleep score tracked with training load become answerable. This is one person's project, offered as-is with no guarantee of uptime, and it holds an OAuth token to your health data — tokens are encrypted at rest with AES-256-GCM and the code is public for that reason. If that trade does not sit right, the same repository documents running your own instance.
What it is
A hosted MCP server that connects to your Withings account over OAuth and exposes your health history as tools an assistant can query.
What you get
- get_sleep_summary — duration, light/deep/REM stages, heart rate, breathing and sleep score
- get_hrv — minute-level RMSSD, SDNN and quality scores captured during sleep
- get_activity and get_intraday_activity — daily steps, distance, calories, elevation, and higher-frequency data through the day
- get_workouts — workout summaries with heart rate zones and metrics
- get_measures — weight, body composition, blood pressure, heart rate, temperature, VO2 max and more
- list_heart_records and get_heart_signal — your ECG recordings and their waveform data
- list_stetho_records and get_stetho_signal — stethoscope recordings, if you have a BPM Core
- get_user_devices and get_user_goals — the devices on the account and the step, sleep and weight goals set on it
Requirements
A Withings account with connected devices, authorized over OAuth. Add https://withings-mcp.com/mcp as a custom connector and approve the permissions in the browser — nothing to install. Access is revocable from your Withings account settings at any time. Self-hosting is documented as well and needs Bun 1.1 or higher, a Withings developer application, and a Supabase project.
Setup effort
Add the hosted endpoint — paste it into your client
USE CASES
01
Understanding why a week of sleep felt bad
Read the nightly sleep summaries with stages and heart rate, and the HRV captured over the same nights, in one pass.
02
Seeing whether a weight trend is real or noise
Pull measures over months rather than eyeballing the app's chart, and look at body composition alongside the number.
03
Comparing training months
Workout summaries with heart rate zones for both periods, compared side by side instead of scrolled through.
04
Looking at an ECG you recorded
List the heart records, then pull the waveform for the one you want to look at more closely.
05
Checking progress against the goals on the account
Read the step, sleep and weight goals and the daily activity together, so 'did I hit it' has an actual answer.
12 tools
Listed in project docs. Your client may show a different list.
get_sleep_summaryget_activityget_intraday_activityget_workoutsget_measuresget_user_devicesget_user_goalslist_heart_recordsget_heart_signallist_stetho_recordsget_stetho_signalBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- A Withings account with connected devices
- A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://withings-mcp.com/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Desktop
Open Claude Desktop → Customize → Connectors
Click + → Add Custom Connector
Set the name to Withings and the URL to https://withings-mcp.com/mcp, then click Add
Click Connect and authorize with your Withings account
Any MCP client
Configure your MCP client with the following connection details:
Server URL: https://withings-mcp.com
Transport: Streamable HTTP
Endpoint: /mcp
Authentication: OAuth 2.0
Discovery URL: /.well-known/oauth-authorization-server
