withings-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
withings-mcp
Read-only Model Context Protocol server for Withings weight and body-composition history. It uses Withings' OAuth 2.0 web flow, refreshes rotating tokens automatically, and persists tokens in a private file (use a Railway volume in production).
Tools
get_measurements: normalized measurements for an inclusive date range.get_weight_history: weight-focused history with kilograms and pounds.get_latest_measurement: most recent weight/body-composition group.get_authorization_status: configuration and authorization state without secrets.
Supported scale metrics include weight, fat-free mass, fat ratio, fat mass, muscle mass, hydration, bone mass, visceral fat, basal metabolic rate, and metabolic age. Availability depends on the scale model and the data Withings returned.
Related MCP server: Withings MCP Client
Environment
Variable | Purpose |
| Withings developer application client ID |
| Withings developer application secret |
| Exact OAuth callback URI registered with Withings |
| Persistent token path; defaults to |
| Bearer token required by |
The service exposes /healthz, /oauth/start, /oauth/callback, and the protected /mcp endpoint. Starting OAuth does not expose data; the callback requires a short-lived Withings code and a one-time server-side state value. Measurement reads still require the separate MCP bearer token.
Local test
python3 -m venv .venv
.venv/bin/pip install --require-hashes -r requirements-dev.lock
.venv/bin/pytestRailway
Mount a volume at /data, set the six variables above, and register this callback in the Withings developer dashboard:
https://<service-domain>/oauth/callbackAfter authorization, connect an MCP client to https://<service-domain>/mcp with Authorization: Bearer <MCP_AUTH_TOKEN>.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Household health records with source attribution. Read and add records with OAuth approval.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Remote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides access to Oura Ring health and fitness data through the Oura API v2, enabling retrieval of sleep, activity, readiness, and other health metrics.128 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables retrieval of health data from Withings smart scales including weight measurements and comprehensive body composition metrics like fat mass, muscle mass, and hydration levels. Supports multiple users, unit preferences, and OAuth authentication for secure access to personal health data.2ISC
- AlicenseAqualityBmaintenanceProvides read-only access to Withings health metrics including body composition, sleep, workouts, and ECG data with local SQLite caching and trend analysis. Features incremental synchronization, automatic OAuth token refresh, and supports all 200+ Withings measurement types for comprehensive health tracking.8567 PyPI1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.45MIT