Provider guide · local-first MCP

Withings MCP server for AI agents

Connect body composition, sleep, activity and conditional heart records to Claude, Cursor or another MCP-compatible agent without placing the OAuth token in model context.

Short answer

A Withings MCP server is a local bridge between the official Withings Public API and an AI agent. Run npx -y withings-mcp-unofficial setup, complete OAuth promptly, verify with npx -y withings-mcp-unofficial doctor, and start with daily or weekly summaries before requesting detailed body, sleep or heart records. For Claude or Cursor, the model receives bounded MCP responses, not the OAuth token.

Choose Withings MCP when

A Withings scale or sleep device is already the source of truth.
The agent needs body composition, sleep and activity in one workflow.
OAuth credentials must stay on the machine running the connector.
Daily and weekly summaries are more useful than continuous telemetry.

Choose another path when

You need raw continuous sensor streams; the public API does not expose them.
The required heart record is unavailable for the account, device or plan.
Your source of truth is Fitbit, Oura, WHOOP or a local Apple Health export.
The workflow is clinical, diagnostic or emergency monitoring.

Setup method

Connect Withings to an AI agent in five checks

1
Create a Withings OAuth app
Use the Withings developer portal and register http://127.0.0.1:3000/callback as the redirect URI.
2
Run the guided setup
Run npx -y withings-mcp-unofficial setup. Request only the scopes the workflow needs; the recommended baseline is user.activity user.metrics.
3
Finish authorization immediately
Complete the local callback without pausing after approval because Withings authorization codes are short-lived.
4
Verify before adding an agent
Run npx -y withings-mcp-unofficial doctor, then call withings_connection_status and withings_privacy_audit before requesting health records.
5
Start with summaries
Prefer withings_daily_summary or withings_weekly_summary. Ask permission before detailed body, sleep or heart records.

Install and verify

terminal

npx -y withings-mcp-unofficial setup
npx -y withings-mcp-unofficial doctor

MCP client configuration

mcp-client.json

{
  "mcpServers": {
    "withings": {
      "command": "npx",
      "args": ["-y", "withings-mcp-unofficial"]
    }
  }
}

What a Withings-aware agent can read

Body measures

Weight, fat percentage, muscle, bone and water when user.metrics and the device expose them.

Activity and workouts

Steps, calories, distance, intensity and sport records through user.activity.

Sleep

Sleep summaries and detail records when supported by the connected Withings device.

Heart records

ECG, blood pressure and related records are conditional on the device, account and plan.

Continuous raw sensor telemetry is not exposed by the Withings Public API. Do not describe a daily or sleep record as a live medical monitor.

Safe first-call sequence

1. withings_connection_status
2. withings_capabilities
3. withings_privacy_audit
4. withings_daily_summary
5. withings_weekly_summary

Privacy boundary

OAuth tokens stay local, and the signed API flow runs inside the connector. Summaries should come before detailed records. Heart, body and sleep data should only be requested for the user-authorized wellness purpose at hand.

Withings MCP questions

What is the Withings MCP server?

The Withings MCP server is the local process provided by withings-mcp-unofficial. It uses the official Withings Public API to expose user-authorized body measures, activity, workouts, sleep and conditional heart records to an MCP-compatible AI client.

Can I connect Withings to Claude or Cursor?

Yes. Run the setup command, finish Withings OAuth, verify the connection with the doctor command and add the documented mcpServers entry to Claude Desktop, Cursor or another MCP-compatible client.

How do I connect Withings to Claude?

Install npx -y withings-mcp-unofficial setup, complete the local Withings OAuth callback, run npx -y withings-mcp-unofficial doctor, and add the connector's mcpServers configuration to Claude Desktop. Start with withings_connection_status and withings_daily_summary before requesting detailed records.

Does the AI model receive my Withings OAuth token?

No. The connector keeps OAuth tokens on the machine running the MCP server. The model receives bounded MCP responses, not the OAuth secret.

Which Withings records can an agent read?

Body measures, daily activity, workouts and sleep are available when the user account, device and scopes expose them. Heart records such as ECG or blood pressure are conditional. Continuous raw sensor telemetry is not available through the Withings Public API.

Is the Withings MCP connector medical advice?

No. It provides personal wellness context and is not a medical device, diagnosis, treatment, emergency monitor or replacement for a qualified clinician.

Continue with the canonical sources

Withings connector specification Compare wellness MCP connectors Delx Wellness security model Machine-readable Markdown

Delx Wellness and withings-mcp-unofficial are not affiliated with Withings. This guide provides technical integration context, not medical advice.