Withings Mcp Unofficial

Name: Withings Mcp Unofficial
Author: davidmosiah

@davidmosiah

代码仓库主页

关于 Withings Mcp Unofficial

Unofficial local-first Withings MCP server for AI health, sleep and activity agents.

基本信息

分类

其他

许可证

MIT

运行时

node

传输方式

stdio

发布者

davidmosiah

提交者

David Batista

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

verify local setup before calling Withings

inventory supported data domains, scopes, privacy modes and recommended first calls without calling Withings APIs.

body, sleep, activity and heart brief for today

scorecard, comparison vs prior week, next-week plan

punctual weight/composition records. Use ISO 8601 `after` / `before` windows for large histories; the server sends Withings `startdate` / `enddate` upstream and caps returned records with `limit`.

heart records when device/plan permit

daily activity summaries

logged workouts

daily sleep summaries with HR/stage fields

detailed sleep records

概览

What is Withings Mcp Unofficial?

A local-first MCP server that connects AI agents to your Withings body measures, sleep, activity and heart data. It handles Withings’ signed OAuth flow, normalizes responses, and exposes the data through the Model Context Protocol. Tokens never leave your machine.

How to use Withings Mcp Unofficial?

Run npx -y withings-mcp-unofficial setup (interactive, paste client ID and secret), then npx -y withings-mcp-unofficial auth (opens browser to capture OAuth code), then npx -y withings-mcp-unofficial doctor to verify readiness. Add the server to your MCP client config as shown in the README.

Key features of Withings Mcp Unofficial

Local-first: OAuth tokens never leave your machine.
Supports body, sleep, activity, and heart data.
Offers diagnostic, summary, and privacy tools.
Privacy mode defaults to structured (raw JSON opt‑in).
Includes a built‑in cache (SQLite).
One‑command setup with Delx Wellness for Hermes.

Use cases of Withings Mcp Unofficial

Get a daily wellness brief combining body, sleep, activity, and heart data.
Investigate body composition and sleep changes over a date range.
Generate a weekly scorecard with next‑week plans.

FAQ from Withings Mcp Unofficial

What data domains does Withings Mcp Unofficial support?

Body measures (weight, fat %, muscle, bone, water), daily activity (steps, calories, distance), workouts, sleep summaries and details, and heart records (ECG, BP, etc.) when device/plan allow. Continuous sensor telemetry is not exposed by the Withings Public API.

What are the runtime requirements?

Node.js 20+ and a Withings app registered at the Withings partner dashboard with redirect URI http://127.0.0.1:3000/callback. Scopes user.activity user.metrics are recommended.

Where are OAuth tokens stored?

Tokens are stored in ~/.withings-mcp/tokens.json with 0600 permissions and are never returned by tools. The server never prints access or refresh tokens.

How does authentication work?

The package handles the signed‑request OAuth flow locally; client secrets never reach the MCP client. The OAuth code is short‑lived (a few minutes). After authorizing, the token is exchanged and stored.

Is this project affiliated with Withings?

No. This is an unofficial project, not affiliated with, endorsed by, or supported by Withings. Use it only with your own Withings account and in line with the Withings Public API terms.