---
title: Withings MCP Server for AI Agents
description: Use a Withings MCP server with Claude, Cursor and other AI agents through a local-first connector, with safe OAuth and bounded responses.
canonical: https://wellness.delx.ai/guides/withings-mcp-for-ai-agents
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Withings MCP Server for AI Agents

## Direct answer

A Withings MCP server is a local bridge between the official Withings Public API and an MCP-compatible AI agent. OAuth tokens stay on the machine running the connector; the model receives bounded MCP responses, not the OAuth secret. For Claude or Cursor, install the connector, finish local OAuth and verify the connection before requesting records.

## Short answer

Run `npx -y withings-mcp-unofficial setup`, complete Withings 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.

## Setup method

1. Create a Withings OAuth app and register `http://127.0.0.1:3000/callback`.
2. Run `npx -y withings-mcp-unofficial setup` and request only the required scopes. Recommended baseline: `user.activity user.metrics`.
3. Finish the callback immediately because Withings authorization codes are short-lived.
4. Run `npx -y withings-mcp-unofficial doctor`, then call `withings_connection_status` and `withings_privacy_audit`.
5. Start with `withings_daily_summary` or `withings_weekly_summary` before detailed records.

## MCP client configuration

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

## Data availability

- Body measures: available. Weight, fat percentage, muscle, bone and water with user.metrics scope.
- Daily activity: available. Steps, calories, distance and intensity.
- Workouts and sport metadata: available. Requires user.activity scope.
- Sleep summaries and detail records: available. Depends on device support.
- Heart records: conditional. ECG, blood pressure and other records vary by device/plan.
- Continuous sensor telemetry: not_available. Not exposed by Withings Public API.

## Safe first-call sequence

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

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.

## Privacy and limits

- OAuth tokens stay local.
- Signed API flow is handled inside the connector.
- Heart and body records are only available when the user's devices and scopes expose them.
- Agents can use summaries before requesting detailed records.
- Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.

- Data varies by Withings device and plan.
- OAuth authorization codes are short-lived.
- No raw continuous telemetry.

## Common questions

### What is the Withings MCP server?

It is the local process provided by `withings-mcp-unofficial`. It exposes user-authorized Withings records to an MCP-compatible AI client through the official Withings Public API.

### Can I connect Withings to Claude or Cursor?

Yes. Complete setup and doctor first, then add the documented `mcpServers` entry to Claude Desktop, Cursor or another compatible client.

### How do I connect Withings to Claude?

Install the connector, complete the local Withings OAuth callback, run the doctor command, add the documented Claude Desktop `mcpServers` entry and start with `withings_connection_status`.

### Does the AI model receive my OAuth token?

No. OAuth tokens stay on the machine running the connector.

### Is this medical advice?

No. This connector provides personal wellness context and is not a medical device, diagnosis, treatment or emergency monitor.

## Canonical sources

- Connector specification: https://wellness.delx.ai/connectors/withings
- Connector comparison: https://wellness.delx.ai/guides/choose-wellness-mcp-connector
- Security model: https://wellness.delx.ai/security
- npm: https://www.npmjs.com/package/withings-mcp-unofficial
- GitHub: https://github.com/davidmosiah/withings-mcp

Delx Wellness and withings-mcp-unofficial are not affiliated with Withings.