All connectors


withings-mcp-unofficial
Withings
A Withings connector that gives agents body composition, sleep, activity, workouts and device-backed heart context.
Body MeasuresSleepActivityHeart Records

OAuth 2.0 signed
Best for body-composition, sleep and cardiometabolic wellness agents that need smart-scale and Withings device records.
Quick Start
terminal
npx -y withings-mcp-unofficial setup
npx -y withings-mcp-unofficial doctormcp-client.json
{
"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
Available
Body measures
Weight, fat percentage, muscle, bone and water with user.metrics scope.
Available
Daily activity
Steps, calories, distance and intensity.
Available
Workouts and sport metadata
Requires user.activity scope.
Available
Sleep summaries and detail records
Depends on device support.
Conditional
Heart records
ECG, blood pressure and other records vary by device/plan.
Not exposed
Continuous sensor telemetry
Not exposed by Withings Public API.
Agent Tools
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
Privacy Model
OAuth tokens stay local.
Signed API flow is handled inside the connector.
Heart and body records are only available when the user's devices and scopes expose them.
Agents can use summaries before requesting detailed records.