---
title: Withings MCP server for AI agents
description: Withings MCP server for smart-scale composition, sleep stages and heart records.
canonical: https://wellness.delx.ai/connectors/withings
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Withings MCP server for AI agents

The Withings MCP server gives agents body composition, sleep, activity, workouts and device-backed heart context through a local-first connector.

## Short answer

The Withings MCP connector for AI agents is a local-first server provided by withings-mcp-unofficial. It uses the official Withings Public API and user-authorized OAuth to expose body measures, activity, workouts, sleep summaries and conditional heart records to an MCP-compatible client. OAuth tokens stay local, authorization codes are short-lived, and continuous raw sensor telemetry is not exposed; data availability depends on the user's device, plan and granted scopes, and Delx does not host a copy of the data.

## Install

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

## Agent client config

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

## Signals

- Body Measures
- Sleep
- Activity
- Heart Records

## 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.

## MCP tools

### Profile and onboarding

- `withings_profile_get`
- `withings_profile_update`
- `withings_onboarding`

### Start here

- `withings_connection_status`
- `withings_daily_summary`
- `withings_weekly_summary`

### Auth and diagnostics

- `withings_capabilities`
- `withings_agent_manifest`
- `withings_privacy_audit`
- `withings_cache_status`
- `withings_get_auth_url`
- `withings_exchange_code`
- `withings_revoke_access`

### Body and metrics

- `withings_list_body_measures`
- `withings_list_heart`

### Activity

- `withings_list_activity`
- `withings_list_workouts`

### Sleep

- `withings_list_sleep_summary`
- `withings_list_sleep`

## Prompts

- `withings_daily_checkin`
- `withings_weekly_review`
- `withings_body_sleep_investigation`

## Resources

- `withings://capabilities`
- `withings://agent-manifest`
- `withings://latest/activity`
- `withings://latest/sleep`
- `withings://summary/daily`
- `withings://summary/weekly`

## Privacy

- 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.

## Best for

- Body composition review
- Sleep and weight trend coaching
- Heart record context
- Weekly wellness planning

## Known limits

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

## Links

- GitHub: https://github.com/davidmosiah/withings-mcp
- npm: https://www.npmjs.com/package/withings-mcp-unofficial
- Legacy docs: https://withingsmcp.vercel.app/
- Provider docs: https://developer.withings.com/api-reference/