# withingsmcp [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/davidmosiah/withingsmcp  
**GitHub Stars:** 5  
**npm Downloads (last month):** 143  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/withingsmcp

## Description
Privacy-first, unofficial Withings MCP server for AI health, sleep, activity and heart-rate agents.

## Tools
Capabilities this server exposes over MCP:

- **withings_connection_status** — verify local setup before calling Withings
- **withings_data_inventory** — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Withings APIs.
- **withings_daily_summary** — body, sleep, activity and heart brief for today
- **withings_weekly_summary** — scorecard, comparison vs prior week, next-week plan
- **withings_list_body_measures** — punctual weight/composition records. Use `after` / `before` as `YYYY-MM-DD` or ISO 8601 for large histories; the server sends Withings `startdate` / `enddate` (Unix seconds) upstream and caps returned records with `limit`.
- **withings_list_heart** — heart records when device/plan permit
- **withings_list_activity** — daily activity summaries
- **withings_list_workouts** — logged workouts
- **withings_list_sleep_summary** — daily sleep summaries with HR/stage fields
- **withings_list_sleep** — detailed sleep records

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "withingsmcp": {
    "command": "npx",
    "args": ["-y","delx-wellness-hermes"],
    "env": {
      "WITHINGS_MCP_HOST": "",
      "WITHINGS_MCP_PORT": "",
      "WITHINGS_MCP_TRANSPORT": ""
    }
  }
}
```

**Requires environment variables:** `WITHINGS_MCP_HOST`, `WITHINGS_MCP_PORT`, `WITHINGS_MCP_TRANSPORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What withingsmcp MCP server does

The withingsmcp MCP server gives an MCP-compatible AI client access to selected data from a user’s Withings account. Supported domains include body measurements, daily activity, workouts, sleep summaries, detailed sleep records, and heart data when the account’s device and plan expose it.

Summary tools provide a current daily brief or a weekly scorecard with comparison to the previous week and a suggested plan for the following week. List tools are available when an agent needs records rather than a high-level interpretation. The project is unofficial and is intended for use with the account owner’s own data.

## How it works

The withingsmcp MCP server uses the Withings Public API and performs the signed OAuth flow locally. Access tokens are saved in `~/.withings-mcp/tokens.json` with `0600` permissions and are not returned by MCP tools. Privacy modes make raw upstream payloads opt-in rather than the default.

Stdio is the default transport. The package can also run a stateless Streamable HTTP endpoint on loopback, with a health route at `/health` and an MCP route at `/mcp`. HTTP mode does not use a session ID. The server converts date filters into the formats expected by different Withings API endpoints and limits returned body-measure records with `limit`.

## Setup and configuration

Create a Withings app in the Withings OAuth dashboard and set its redirect URI to `http://127.0.0.1:3000/callback`. Run the interactive setup command to provide the client ID and secret, then run the authentication command to authorize the account in a browser. The doctor command checks whether the local configuration is ready.

The recommended OAuth scopes are `user.activity` and `user.metrics`. After authentication, add the package as an MCP server using an `npx` command and the `withings-mcp-unofficial` package name. Claude Desktop users can run the client-specific setup command to write the configuration. OAuth authorization codes expire quickly, so the browser approval should be followed promptly by code exchange.

For HTTP mode, run the package with `--http`. `WITHINGS_MCP_HOST`, `WITHINGS_MCP_PORT`, and `WITHINGS_MCP_TRANSPORT=http` configure the HTTP listener and transport.

## Tools and capabilities

The withingsmcp MCP server includes:

- Connection and inventory checks that confirm local setup and describe supported domains, scopes, privacy modes, and suggested initial calls without contacting Withings.
- Daily and weekly summaries covering body, sleep, activity, and available heart information.
- Body-measure queries for weight and composition records, with `after`, `before`, and `limit` controls.
- Activity and workout queries for daily summaries and logged exercise.
- Sleep summary queries with duration, stages, efficiency, and heart-rate fields, plus detailed sleep records.
- Heart-record queries when the connected device and plan support them.

Additional diagnostics and account tools cover capabilities, the agent manifest, privacy auditing, cache status, authorization URL generation, code exchange, and access revocation.

## Limitations and notes

Available data depends on the granted scopes, connected devices, Withings plan, and the behavior of the official API. Body measures and heart records use the `user.metrics` scope; activity, workouts, and sleep use `user.activity`. Detailed sleep data is available only when the device exposes it, and heart data varies by device and plan.

The API does not expose continuous sensor telemetry. Records described as raw are upstream Withings JSON for supported endpoints, not direct device sensor streams. The project is not affiliated with, endorsed by, or supported by Withings, and use must follow the Withings Public API terms.

_Full upstream README: https://allmcps.com/mcp/withingsmcp/readme_