Withingsmcp

Name: Withingsmcp
Author: davidmosiah

by davidmosiahversion 0.4.7i★ –iRuns on your computer

Registry nameio.github.davidmosiah/withingsmcp

Install

Overview

Description from the maker (original English)

Privacy-first, unofficial Withings MCP server for AI health, sleep, activity and heart-rate agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health
You need to fill in: WITHINGS_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: WITHINGS_CLIENT_ID, WITHINGS_CLIENT_SECRET, WITHINGS_REDIRECT_URI, WITHINGS_TOKEN_PATH, WITHINGS_PRIVACY_MODE, WITHINGS_CACHE, WITHINGS_CACHE_PATH, WITHINGS_NO_CACHE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "withingsmcp": {
      "command": "npx",
      "args": [
        "-y",
        "withings-mcp-unofficial"
      ],
      "env": {
        "WITHINGS_CLIENT_ID": "your-value",
        "WITHINGS_CLIENT_SECRET": "your-value",
        "WITHINGS_REDIRECT_URI": "your-value",
        "WITHINGS_TOKEN_PATH": "your-value",
        "WITHINGS_PRIVACY_MODE": "your-value",
        "WITHINGS_CACHE": "your-value",
        "WITHINGS_CACHE_PATH": "your-value",
        "WITHINGS_NO_CACHE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add withingsmcp --env WITHINGS_CLIENT_ID=your-value --env WITHINGS_CLIENT_SECRET=your-value --env WITHINGS_REDIRECT_URI=your-value --env WITHINGS_TOKEN_PATH=your-value --env WITHINGS_PRIVACY_MODE=your-value --env WITHINGS_CACHE=your-value --env WITHINGS_CACHE_PATH=your-value --env WITHINGS_NO_CACHE=your-value -- npx -y withings-mcp-unofficial

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "withingsmcp": {
      "command": "npx",
      "args": [
        "-y",
        "withings-mcp-unofficial"
      ],
      "env": {
        "WITHINGS_CLIENT_ID": "your-value",
        "WITHINGS_CLIENT_SECRET": "your-value",
        "WITHINGS_REDIRECT_URI": "your-value",
        "WITHINGS_TOKEN_PATH": "your-value",
        "WITHINGS_PRIVACY_MODE": "your-value",
        "WITHINGS_CACHE": "your-value",
        "WITHINGS_CACHE_PATH": "your-value",
        "WITHINGS_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "withingsmcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "withings-mcp-unofficial"
      ],
      "env": {
        "WITHINGS_CLIENT_ID": "your-value",
        "WITHINGS_CLIENT_SECRET": "your-value",
        "WITHINGS_REDIRECT_URI": "your-value",
        "WITHINGS_TOKEN_PATH": "your-value",
        "WITHINGS_PRIVACY_MODE": "your-value",
        "WITHINGS_CACHE": "your-value",
        "WITHINGS_CACHE_PATH": "your-value",
        "WITHINGS_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WITHINGS_CLIENT_ID env
Withings OAuth client ID. Optional when configured with withings-mcp-server setup.
WITHINGS_CLIENT_SECRET secret env
Withings OAuth client secret. Prefer withings-mcp-server setup so this secret is stored in ~/.withings-mcp/config.json instead of MCP client config.
WITHINGS_REDIRECT_URI env
Redirect URI configured in the Withings Developer Dashboard. Optional when configured with withings-mcp-server setup.
WITHINGS_TOKEN_PATH env
Optional local path for OAuth tokens. Defaults to ~/.withings-mcp/tokens.json.
WITHINGS_PRIVACY_MODE env
Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Withings API payloads, not continuous 24/7 raw sensor telemetry.
WITHINGS_CACHE env
Optional SQLite cache toggle. Set to true or sqlite to enable.
WITHINGS_CACHE_PATH env
Optional local SQLite cache path. Defaults to ~/.withings-mcp/cache.sqlite.
WITHINGS_NO_CACHE env
Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless. Note: Withings's wbsapi.withings.net is POST-only to…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account davidmosiah, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 1025 servers in this category
Published to the registry more recently than 19% of the other 1025 servers in this category
Basic checks equal to or better than 100% of the other 1025 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Withingsmcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WITHINGS_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.7) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Langcare MCP FHIR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated yesterday

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 10 days ago

Install

Langcare MCP FHIR

by langcare

An MCP FHIR server written in Go for EMR systems like Epic and Cerner

Runs on your computer★ 70MITUpdated 9 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Upgrading to 0.6.0: read the migration guide for local-only HTTP, disabled authenticated-response caching, and stricter input/profile limits.

Withings MCP

Give your AI agent your Withings body measures, sleep, activity and heart data — locally.

Local-first MCP server — tokens never leave your machine .

⚡ One-command install with Delx Wellness for Hermes:

npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y withings-mcp-unofficial --http

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

Env: WITHINGS_MCP_HOST, WITHINGS_MCP_PORT, WITHINGS_MCP_TRANSPORT=http.

Local-first MCP server that connects AI agents to your Withings body, sleep, activity and heart data.

Unofficial project. Not affiliated with, endorsed by or supported by Withings. Withings is a trademark of its respective owner. Use this only with your own Withings account and in line with the Withings Public API terms.

Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about body composition, sleep and long-term health trends — without copy-pasting numbers from the Withings app.

Part of Delx Wellness, a registry of local-first wellness MCP connectors.

If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.

Why this exists

Withings has the longest-running consumer body-composition and sleep ecosystem (smart scales, Sleep Analyzer, ScanWatch). The data is rich — punctual weight + body fat + muscle mass measurements, sleep stages, ECG-grade heart records — but the Withings Public API uses a signed-token OAuth flow that's heavier than most consumer APIs.

This package handles the signed OAuth dance locally, normalizes responses, and exposes Withings through the Model Context Protocol. Tokens never leave your machine. Privacy-mode defaults keep raw payloads opt-in.

Setup in 60 seconds

You'll need a Withings app (create one here) with redirect URI http://127.0.0.1:3000/callback.

npx -y withings-mcp-unofficial setup    # interactive: paste client id + secret

npx -y withings-mcp-unofficial auth # opens browser, captures the OAuth code npx -y withings-mcp-unofficial doctor # verifies you're ready

Recommended scopes:

user.activity user.metrics

Then add this to your MCP client config:

"mcpServers": { "withings": { "command": "npx", "args": ["-y", "withings-mcp-unofficial"] } } }

For Claude Desktop, run setup --client claude and the snippet is written for you.

Note: Withings OAuth authorization codes are short-lived (a few minutes). Don't pause between approving the consent screen and withings_exchange_code running.

Try it with your agent

Three things to ask first:

Use withings_connection_status to check setup, then run withings_daily_summary.

Give me a 5-line wellness brief for today.

Call withings_weekly_summary with response_format=json. Identify my biggest

sleep/body bottleneck and give me a next-week plan.

Use the withings_body_sleep_investigation prompt, after=2026-04-01.

Walk me through what changed in body composition + sleep.

Data availability

This package uses the official Withings Public API. When this README says raw, it means the upstream Withings JSON for a supported endpoint — not raw device sensor streams.

Data	Available	Notes
Body measures (weight, fat %, muscle, bone, water)	✓	Requires `user.metrics` scope
Daily activity (steps, calories, distance, intensity)	✓	Requires `user.activity` scope
Workouts + sport metadata	✓	Requires `user.activity` scope
Sleep summaries (duration, stages, efficiency, HR)	✓	Requires `user.activity` scope
Sleep detail records	✓	When the device exposes them
Heart records (ECG, BP, etc.)	✓	Requires `user.metrics` scope; varies by device/plan
Continuous sensor telemetry	—	Not exposed by Withings Public API

Tools

Start with these:

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

Auth & diagnostics

withings_capabilities, withings_agent_manifest, withings_privacy_audit, withings_cache_status
withings_get_auth_url, withings_exchange_code, withings_revoke_access

Body & metrics

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 (Unix seconds) upstream and caps returned records with limit.
Date filters are action-aware: getactivity / getworkouts / sleep getsummary send civil startdateymd / enddateymd; getmeas, sleep detail, and heart list keep epoch startdate / enddate. Offset ISO instants keep their exact epoch conversion on epoch-style actions.
withings_list_heart — heart records when device/plan permit

Activity

withings_list_activity — daily activity summaries
withings_list_workouts — logged workouts

Sleep

withings_list_sleep_summary — daily sleep summaries with HR/stage fields
withings_list_sleep — detailed sleep records

Prompts

withings_daily_checkin — practical daily health and body check-in
withings_weekly_review — review trends across body, sleep, activity
withings_body_sleep_investigation — investigate body measures + sleep together

Resources

withings://capabilities, withings://agent-manifest
withings://latest/activity, withings://latest/sleep
withings://summary/daily, withings://summary/weekly

Privacy & security

OAuth tokens are stored in ~/.withings-mcp/tokens.json with 0600 permissions and are never returned by tools.
Withings uses a signed-request OAuth flow — the package handles signing locally; client secrets never reach the MCP client.
The server never prints access or refresh tokens.
WITHINGS_PRIVACY_MODE defaults to structured. Raw Withings JSON is opt-in via raw mode or per-call override.
Structured mode preserves complete upstream physiological fields, including future Withings additions, while removing GPS and secret-bearing values.
withings_revoke_access clears local tokens; full account-side token revocation depends on your Withings plan.
The MCP client never sees access or refresh tokens.
This is not medical advice. Withings exposes data that may resemble medical signals (ECG, blood pressure) but this server is for personal AI workflows, not diagnosis or treatment.

Configuration

setup writes most of these into ~/.withings-mcp/config.json (0600). Manual env override is supported:

WITHINGS_CLIENT_ID=…

WITHINGS_CLIENT_SECRET=… WITHINGS_REDIRECT_URI=http://127.0.0.1:3000/callback

Optional

WITHINGS_SCOPES="user.activity user.metrics" WITHINGS_PRIVACY_MODE=structured # summary | structured | raw WITHINGS_CACHE=sqlite # legacy setting; authenticated caching is disabled WITHINGS_TOKEN_PATH=~/.withings-mcp/tokens.json WITHINGS_CACHE_PATH=~/.withings-mcp/cache.sqlite

Hermes / remote setup

npx -y withings-mcp-unofficial setup --client hermes --no-auth

npx -y withings-mcp-unofficial auth # run locally if browser auth is needed npx -y withings-mcp-unofficial doctor --client hermes hermes mcp test withings

After Hermes config changes, use /reload-mcp or hermes mcp test withings. Don't restart the gateway for normal data access.

If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.withings-mcp/tokens.json to the server with chmod 600.

Requirements

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

Development

git clone https://github.com/davidmosiah/withings-mcp.git

cd withings-mcp npm install npm test npm run build

Test with MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Withingsmcp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Langcare MCP FHIR

README from the maker

HTTP (v2 stateless)

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

Why this exists

Setup in 60 seconds

Try it with your agent

Data availability

Tools

Prompts

Resources

Privacy & security

Configuration

Optional

Hermes / remote setup

Requirements

Development

Links