withingsmcp

Withingsmcp MCP Server

Withings body measurements, sleep records and activity logs become available to personal AI workflows through withingsmcp. This unofficial, local-first connector serves Withings account holders using MCP-compatible agents to review their wellness data.

Server facts

withingsmcp MCP Server

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
5
Last commit
Data as of

Overview

Daily check-ins and weekly reviews bring together Withings body composition, sleep, activity and available heart records. Agents can request individual measurement histories, daily activity totals, workouts, sleep summaries or detailed sleep entries where supported. The daily summary assembles a wellness brief, while the weekly summary highlights trends, bottlenecks and possible actions. A separate wellness-context tool converts sleep and activity information into a shared format for recommendation engines. Heart data availability depends on the device and plan; continuous sensor streams are not available through the Withings Public API.

Connection checks and a data inventory help establish local readiness and supported data before requesting account records. Setup guidance and OAuth tools support authorization, with signing handled locally and tokens excluded from tool responses. Structured output is the default privacy mode, while upstream JSON requires opting in. The connector also reads a shared Delx Wellness profile and provides onboarding questions; saving profile changes requires explicit user intent. Local access removal deletes the token file rather than guaranteeing account-side revocation. This unofficial integration supports personal wellness workflows, not medical diagnosis or treatment.

withingsmcp setup notes

  • withingsmcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers