withings-mcp-unofficial
Withings MCP server for AI agents
The Withings MCP server gives agents body composition, sleep, activity, workouts and device-backed heart context through a local-first connector.
Best for body-composition, sleep and cardiometabolic wellness agents that need a local Withings MCP connector for smart-scale and device records.
MCP server answers
The Withings MCP connector for AI agents is a local-first server provided by withings-mcp-unofficial. It uses the official Withings Public API and user-authorized OAuth to expose body measures, activity, workouts, sleep summaries and conditional heart records to an MCP-compatible client. OAuth tokens stay local, authorization codes are short-lived, and continuous raw sensor telemetry is not exposed; data availability depends on the user's device, plan and granted scopes, and Delx does not host a copy of the data.
Compare this connector with the other wellness pathsFollow the Withings MCP setup and safe first-call guideWhat is the Withings MCP server?
The Withings MCP connector for AI agents is a local-first server provided by withings-mcp-unofficial. It uses the official Withings Public API and user-authorized OAuth to expose body measures, activity, workouts, sleep summaries and conditional heart records to an MCP-compatible client. OAuth tokens stay local, authorization codes are short-lived, and continuous raw sensor telemetry is not exposed; data availability depends on the user's device, plan and granted scopes, and Delx does not host a copy of the data.
How do I install Withings MCP?
Run npx -y withings-mcp-unofficial setup, then npx -y withings-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.
What can an agent read from Withings?
The available records start with Body measures, Daily activity, Workouts and sport metadata, Sleep summaries and detail records. Check Data Availability for scope, device and export limitations before using any result.
Quick Start
npx -y withings-mcp-unofficial setup
npx -y withings-mcp-unofficial doctor{
"mcpServers": {
"withings": {
"command": "npx",
"args": ["-y", "withings-mcp-unofficial"]
}
}
}- 01
Create a Withings OAuth app.
- 02
Use redirect URI http://127.0.0.1:3000/callback.
- 03
Do not pause after approval because Withings authorization codes are short-lived.
Recommended scopes
user.activity user.metrics
Data Availability
Body measures
Weight, fat percentage, muscle, bone and water with user.metrics scope.
Daily activity
Steps, calories, distance and intensity.
Workouts and sport metadata
Requires user.activity scope.
Sleep summaries and detail records
Depends on device support.
Heart records
ECG, blood pressure and other records vary by device/plan.
Continuous sensor telemetry
Not exposed by Withings Public API.
Agent Tools
Profile and onboarding
- withings_profile_get
- withings_profile_update
- withings_onboarding
Start here
- withings_connection_status
- withings_daily_summary
- withings_weekly_summary
Auth and diagnostics
- withings_capabilities
- withings_agent_manifest
- withings_privacy_audit
- withings_cache_status
- withings_get_auth_url
- withings_exchange_code
- withings_revoke_access
Body and metrics
- withings_list_body_measures
- withings_list_heart
Activity
- withings_list_activity
- withings_list_workouts
Sleep
- withings_list_sleep_summary
- withings_list_sleep
Prompts and Resources
Prompts
- withings_daily_checkin
- withings_weekly_review
- withings_body_sleep_investigation
Resources
- withings://capabilities
- withings://agent-manifest
- withings://latest/activity
- withings://latest/sleep
- withings://summary/daily
- withings://summary/weekly