Skip to main content
Glama
stefanocaronia

withings-mcp

by stefanocaronia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WITHINGS_MCP_DIRNoOverride the directory where config.json and tokens.json are stored. Defaults to %LOCALAPPDATA%\withings-mcp\ on Windows, $XDG_CONFIG_HOME/withings-mcp or ~/.config/withings-mcp elsewhere.
WITHINGS_CLIENT_IDNoWithings client ID, takes precedence over config.json.
WITHINGS_CLIENT_SECRETNoWithings client secret, takes precedence over config.json.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
withings_statusB

Whether the Withings account is connected, which scopes were granted and when the access token expires.

withings_devicesB

Devices paired to the account (model, type, battery, last sync).

withings_measurementsA

Body measurements (scale, blood pressure monitor, thermometer, ECG) grouped by measurement session.

types filters by comma-separated names or Withings type ids, e.g. "weight,fat_ratio,muscle_mass" or "1,6,76"; omit it for everything. Names: weight, height, fat_free_mass, fat_ratio, fat_mass, diastolic_bp, systolic_bp, heart_rate, temperature, spo2, body_temperature, skin_temperature, muscle_mass, hydration, bone_mass, pulse_wave_velocity, vo2_max, afib_ecg, qrs_interval, pr_interval, qt_interval, qtc_interval, afib_ppg, vascular_age, extracellular_water, intracellular_water, visceral_fat, basal_metabolic_rate, metabolic_age. Values are already decoded into the unit in the key (weight_kg, fat_ratio_pct, systolic_bp_mmHg, ...). include_manual=false keeps only device-captured groups (drops manual entries).

withings_activityC

Daily activity summaries: steps, distance (m), elevation (floors), soft/moderate/intense/active durations (s), calories (active, kcal), totalcalories, heart rate average/min/max and hr_zone_0..3 durations (s).

withings_sleepC

Nightly sleep summaries: time in bed / asleep, light/REM/deep durations (s), efficiency, latency, wake-ups, heart and respiration rate, breathing disturbances, snoring, sleep_score, HRV (rmssd). date is the night's date.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool maps to a clearly distinct data domain: connection status, devices, body measurements, activity, and sleep. There is no overlap in purpose, and the descriptions anchor each to a specific resource. An agent can select the right tool unambiguously.

Naming Consistency5/5

All five tools follow the same predictable withings_<noun> pattern (status, devices, measurements, activity, sleep). No verb-style mixing or case inconsistencies. The naming is uniform and readable.

Tool Count4/5

Five tools is well-scoped and each earns its place by covering a major Withings data category. It is slightly thin in that related surfaces (e.g. workouts, user profile) are not exposed, but nothing feels redundant or padded.

Completeness4/5

The set provides solid read coverage across status, devices, measurements, activity, and sleep, covering the core lifecycle of a health-data reader. Minor gaps remain, such as workouts or intraday data, but core agent workflows are supported without dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources