Withingsmcp MCP Server

Withingsmcp MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Privacy-first, unofficial Withings MCP server for AI health, sleep, activity and heart-rate agents.

What you get

What the assistant can call

Once Withingsmcp is connected, these are the calls the assistant has available:

• withings_connection_status — verify local setup before calling Withings
• withings_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Withings APIs
• withings_daily_summary — body, sleep, activity and heart brief for today
• withings_weekly_summary — scorecard, comparison vs prior week, next-week plan
• withings_list_body_measures — punctual weight/composition records. Use after / before as YYYY-MM-DD or ISO 8601 for large histories; the server sends Withings startdate / enddate
• withings_list_heart — heart records when device/plan permit
• withings_list_activity — daily activity summaries
• withings_list_workouts — logged workouts
• withings_list_sleep_summary — daily sleep summaries with HR/stage fields
• withings_list_sleep — detailed sleep records

Setting it up

delx-wellness-hermes on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 4 environment variables: WITHINGS_CLIENT_ID, WITHINGS_CLIENT_SECRET, WITHINGS_TOKEN_PATH, WITHINGS_CACHE_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 20+ - A Withings app at https://account.withings.com/partner/dashboard_oauth2 with redirect URI http://127.0.0.1:3000/callback

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Withingsmcp's toolset — withings_connection_status, withings_data_inventory, withings_daily_summary and 7 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Withingsmcp.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the withingsmcp mcp server does with a few real requests.