mcp-server-withings
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WITHINGS_REDIRECT_URI | Yes | The redirect URI for the Withings app, must match exactly. | |
| WITHINGS_ENABLE_WRITES | No | Set to 'true' to enable write tools. | false |
| WITHINGS_ENCRYPTION_KEY | Yes | AES-256-GCM encryption key for the token store, never commit. | |
| WITHINGS_TRUST_FORWARDED_USER | No | Set to 'true' when behind a gateway that forwards X-MCP-User. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| withings_search_capabilitiesA | Find the right Withings tool. Use first. |
| withings_connectA | Start linking YOUR Withings account. Returns an authorization URL — open it in your browser, sign into Withings, and approve. After that the data tools work. Needed once (and again only if you disconnect or the link expires). |
| withings_statusA | Whether your Withings account is linked and token freshness. |
| withings_disconnectA | Remove your stored Withings tokens from this server. |
| withings_get_measuresA | Body measurements by type + date range. Common meastypes: 1=weight,5=fat-free mass,6=fat ratio %,8=fat mass,9=diastolic,10=systolic,11=heart pulse,54=SpO2,76=muscle mass,77=hydration,88=bone mass. Defaults to weight+composition. |
| withings_get_activityA | Daily steps/calories/distance/active minutes for a date range. |
| withings_get_sleepA | Per-night sleep summary, or high-frequency sleep phases with detailed=true. |
| withings_get_workoutsC | Logged workouts with type, duration, calories, HR. |
| withings_get_heartA | List heart/ECG recordings for a date range, or fetch one ECG signal by signalId. |
| withings_get_devicesC | Your linked Withings devices. |
| withings_get_goalsC | Your step/sleep/weight goals. |
| withings_add_measureA | Manually log a body measurement (e.g. weight in kg). Requires write access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target distinct resource types (activity, sleep, workouts, heart, devices, goals, measures), and descriptions clearly separate them. Minor overlap exists between heart recordings and heart pulse in measures, and the meta-tool search_capabilities adds an explicit routing step, but overall boundaries are clear.
All tools share the withings_ prefix and most follow a verb_noun pattern (get_*, add_*, search_*). However, withings_status is a bare noun and withings_connect/disconnect have no object, deviating slightly from the otherwise consistent pattern.
12 tools is well-scoped for a health data integration server, covering data retrieval, manual logging, and account lifecycle without feeling bloated or sparse.
The surface covers major Withings data domains (activity, sleep, workouts, heart, body measures, devices, goals) plus auth status and linking. Missing write operations like updating goals or deleting measures are minor gaps, but the read-side coverage is comprehensive.