Overview
What is Withings?
An MCP server that brings your Withings health data into Claude or any MCP-compatible client. It gives natural‑language access to sleep patterns, body measurements, workouts, heart data, and more, using OAuth 2.0 to connect to the Withings API.
How to use Withings?
For end users: add a custom connector in Claude Desktop (Settings → Connectors → Add Custom Connector) with the remote MCP server URL https://withings-mcp.com/mcp, then authorize via OAuth. Developers can self‑host by cloning the repo, setting environment variables (Client ID, Secret, Redirect URI, Encryption Secret), building with npm run build, and deploying.
Key features of Withings
- Access sleep, activity, body measurements, workouts, and heart data
- Tools for sleep summary, activity, intraday activity, workouts, measures, devices, goals, heart records, and stethoscope data
- AES-256-GCM encryption of all tokens at rest
- Privacy‑safe logging that automatically redacts sensitive information
- OAuth 2.0 authentication with Withings
- Self‑hosting option for developers (Node.js 18+ and Deno CLI required)
Use cases of Withings
- Ask Claude about your sleep quality, duration, and stages over the past week
- Track weight trends, body composition, and blood pressure over time
- Review workout summaries with heart rate zones and compare monthly intensity
- Monitor ECG recordings and detailed heart data
- Set and check your fitness and health goals through conversation
FAQ from Withings
What data does the server access?
It accesses sleep patterns, body measurements, activity/workout data, heart health (ECG), stethoscope recordings (if you have BPM Core), user devices, and user goals from your Withings account.
How is my data kept private?
All authentication tokens are encrypted at rest using AES-256-GCM. The code is public and privacy‑safe logging automatically redacts tokens, user IDs, and credentials from logs. You can revoke access anytime from your Withings account settings.
What are the runtime requirements for self‑hosting?
Node.js 18+ and npm, plus Deno CLI for deployment. A publicly accessible URL is required for Withings OAuth callbacks (localhost is not supported by Withings).
Does the server support both hosted and self‑hosted modes?
Yes. End users can use the public hosted server at https://withings-mcp.com/mcp without hosting anything. Developers can also self‑host by following the detailed setup guide.
What transport and authentication does the server use?
It uses Server‑Sent Events (SSE) transport with an endpoint at /mcp. Authentication is OAuth 2.0 via a discovery URL at /.well-known/oauth-authorization-server.
