Withings MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WITHINGS_CLIENT_ID | Yes | Your Withings API Client ID from the Developer Dashboard | |
| WITHINGS_ACCESS_TOKEN | Yes | Your Withings OAuth2 access token (generated during authentication) | |
| WITHINGS_REDIRECT_URI | No | The redirect URI configured in your Withings application | http://localhost:8080/callback |
| WITHINGS_CLIENT_SECRET | Yes | Your Withings API Client Secret from the Developer Dashboard | |
| WITHINGS_REFRESH_TOKEN | Yes | Your Withings OAuth2 refresh token (generated during authentication) |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_infoA | Get user information from Withings account |
| get_measurementsB | Get body measurements (weight, fat mass, muscle mass, etc.) |
| get_activityB | Get daily activity data (steps, calories, distance, elevation) |
| get_sleep_summaryC | Get sleep summary data (duration, deep sleep, REM, wake up count, breathing disturbances, apnea, etc.) |
| get_sleep_detailsB | Get detailed sleep data with all sleep phases |
| get_workoutsC | Get workout/training sessions data |
| get_heart_rateC | Get heart rate measurements over a time period |
| get_authorization_urlA | Get OAuth2 authorization URL to authenticate with Withings |
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 8 tools
All tools have clearly distinct purposes: activity, heart rate, body measurements, sleep details vs summary, workouts, user info, and authorization. Even the two sleep tools are well-differentiated by detail level.
All tools follow a perfect 'get_<resource>' pattern with snake_case, making it predictable and easy for an agent to infer tool purposes.
With 8 tools, the server covers a comprehensive but focused set of health data endpoints without being overwhelming or too sparse.
The server covers all major Withings health metrics (activity, heart, sleep, workouts, body measurements, user info). Missing write operations and some niche metrics like blood pressure, but core read functionality is complete.