Integration

Withings integration

Withings makes connected health devices (scales, blood pressure monitors, watches, sleep analyzers, thermometers). With a user's authorization, read their body measures (weight, body composition, blood pressure, temperature, SpO2), daily and intraday activity, workouts, sleep summaries and minute-level sleep data, ECG and stethoscope recordings, linked devices and goals; confirm ambiguous measures; manage existing data-update notification subscriptions; and switch raw sensor data capture on or off. Routes that need a signed request (creating notification subscriptions, the full ECG signal, user and order management, dropshipment, nudges, surveys), the partner device link and unlink routes and the OAuth administration routes are not included. Authentication is OAuth 2.0 with a Withings developer application (scopes user.info, user.metrics, user.activity, comma-separated); the access token lasts 3 hours and is refreshed automatically. Withings answers HTTP 200 even on errors: check the status field (0 is success). The standard plan allows 120 requests per minute per application.

Connect Withings How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Withings.Built from the 19 Withings tools below, on the connection you add once.

What you can do with Withings

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Notification subscription, 4 operations

get_notification_subscriptionGet notification subscriptionPOSTReturns the notification subscription the user has for a callback URL and appli category (appli 1 when left out).
list_notification_subscriptionsList notification subscriptionsPOSTLists the user's notification subscriptions (callback URL, appli category, comment), optionally filtered by appli.
revoke_notification_subscriptionRevoke notification subscriptionPOSTDisables this user's notifications sent to callbackurl (Withings: disables all notifications for the user), optionally for one appli category. Missed notifications are never redelivered: backfill with lastupdate.
update_notification_subscriptionUpdate notification subscriptionPOSTChanges one existing subscription, found by callbackurl + appli: send exactly one of new_callbackurl, new_appli or comment. If several match, only one is updated.

Activity, 2 operations

get_intraday_activityGet intraday activityPOSTReturns high-frequency activity samples (steps, heart rate, SpO2, calories...) for a time window, keyed by unix timestamp under series. Only the first 24 hours after startdate are returned.
list_daily_activityList daily activityPOSTLists daily aggregated activity (steps, distance, calories, heart rate zones...) per day. Give startdateymd + enddateymd, or lastupdate. List the metrics you want in data_fields: a metric not requested is not returned.

Measure, 2 operations

confirm_measure_groupConfirm measure groupPOSTTells Withings whether a measure group (grpid from list_measures) belongs to this user. Use it for measures attributed ambiguously (attrib 1).
list_measuresList measuresPOSTLists the user's body measures (weight, fat, blood pressure, temperature, SpO2...) as measure groups. Real value = value x 10^unit. Filter by meastype(s), dates or lastupdate; page with offset while more is 1.

Raw data collection, 2 operations

activate_raw_data_collectionActivate raw data collectionPOSTStarts raw data capture (accelerometer or optical) on a set-up device until enddate. Capture begins at the device's next sync with the Withings app and stops by itself at enddate.
deactivate_raw_data_collectionDeactivate raw data collectionPOSTStops raw data capture on a device. It takes effect at the device's next sync with the Withings app.

Sleep, 2 operations

get_sleep_seriesGet sleep seriesPOSTReturns minute-level sleep data (sleep state, heart rate, respiration, snoring...) between startdate and enddate. Only the first 24 hours after startdate are returned. Request vitals with data_fields.
list_sleep_summariesList sleep summariesPOSTLists one sleep summary per night (time in bed, sleep stages, sleep score, heart and breathing rates...). Give startdateymd + enddateymd, or lastupdate. List the metrics you want in data_fields.

Stethoscope recording, 2 operations

get_stethoscope_signalGet stethoscope signalPOSTReturns one stethoscope recording: the A-law G.711 encoded signal samples with frequency, duration and format. Pass signalid from list_stethoscope_recordings.
list_stethoscope_recordingsList stethoscope recordingsPOSTLists stethoscope recordings (signalid, valvular heart disease flag vhd, device, time) for a period. Pass a signalid to get_stethoscope_signal for the signal itself.

Device, 1 operation

list_devicesList devicesPOSTLists the devices linked to the user (type, model, battery, firmware, last session date, hash_deviceid). Use hash_deviceid with the raw data tools.

Ecg recording, 1 operation

list_ecg_recordingsList ecg recordingsPOSTLists ECG recordings with their atrial fibrillation classification, and blood pressure when taken with BPM Core, for a period. Page with offset while more is true.

Goal, 1 operation

get_user_goalsGet user goalsPOSTReturns the user's goals: daily steps, sleep duration (seconds) and target weight (value x 10^unit kg).

Raw data, 1 operation

list_raw_dataList raw dataPOSTReturns raw sensor records (accelerometer or optical) captured by one device between startdate and enddate. Pass hash_deviceid from list_devices; collection must have been activated.

Workout, 1 operation

list_workoutsList workoutsPOSTLists workouts (category, start and end time, device, details such as calories, distance, heart rate). Give startdateymd + enddateymd, or lastupdate. Request detail metrics with data_fields.

Use Withings from Claude Code, Cursor or Codex

Connect Withings in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Withings operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Withings

Create your workspace
Sign up free. Nothing to install.
Connect Withings once
Add your Withings connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.