partymola/withings-mcp

MCP server for the Withings Health API with OAuth, local SQLite cache, and trend analysis.
**What makes this different from other Withings MCP servers:**
- Local SQLite cache for fast offline queries and historical trend analysis
- Incremental sync - only fetches new data since last sync
- Broad Withings coverage: 17 body-composition metrics plus sleep, daily activity, workouts, and ECG/AFib
- Automatic OAuth token refresh (access tokens: 3h, refresh tokens: 1 year)
- Zero dependencies beyond mcp (HTTP via stdlib)
- Python 3.13+ (tested on 3.13 and 3.14, on Linux, macOS and Windows, in CI)
Tools
| Tool | Description | Data source |
|------|-------------|-------------|
| withings_sync | Sync data from Withings API to local cache | Live API -> SQLite |
| withings_get_body | Body composition (weight, fat%, muscle, bone, BP, SpO2) | Local cache (auto-syncs if stale) |
| withings_get_sleep | Sleep summaries, or detailed phase time-series with detail=True | Cache (summary) / live (detail) |
| withings_get_activity | Daily steps, distance, calories, active time | Local cache (auto-syncs if stale) |
| withings_get_workouts | Workout sessions with type, duration, HR | Local cache (auto-syncs if stale) |
| withings_get_heart | ECG recordings and AFib detection | Live API (always) |
| withings_get_devices | Connected devices with battery status | Live API (always) |
| withings_trends | Period averages, weekly/monthly/quarterly trends, comparisons | Local cache (auto-syncs if stale) |
The cache-backed query tools auto-sync when their data is stale, and accept live=True to bypass the cache and fetch straight from the Withings API. withings_get_heart and withings_get_devices are always live. withings_get_sleep(detail=True) returns minute-by-minute sleep phases (live, up to 7 days per request).
Prerequisites
- Python 3.13+ (tested on 3.13 and 3.14, on Linux, macOS and Windows, in CI)
- uv (recommended) or pip
- A Withings developer account and registered application
Installation
Or run it without installing with uvx withings-mcp. For development from a clone:
Setup
1. Register a Withings app
1. Go to https://developer.withings.com/dashboard
2. Create a new application
3. Set the callback URL to http://localhost:8585
4. Note your Client ID and Client Secret
2. Authenticate
This opens your browser for Withings authorization. After approving, tokens are saved locally in config/.
3. Register with Claude Code
4. First sync
In Claude Code, say: "Sync my Withings data"
This runs withings_sync to populate the local cache. Subsequent syncs only fetch new data.
If anything does not work - no data where you expect it, a sync that stops happening - run withings-mcp doctor. It reports the paths and credentials actually in use and what needs fixing, without making an API call.
You can also sync from the command line without an MCP client:
CLI
Configuration