Withingsmcp

Name: Withingsmcp
Author: davidmosiah

作者：davidmosiah版本 0.4.7i★ –i在你的电脑上运行

注册名称io.github.davidmosiah/withingsmcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 379/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 诊所与健康
你需要填写：WITHINGS_CLIENT_SECRET

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： WITHINGS_CLIENT_ID, WITHINGS_CLIENT_SECRET, WITHINGS_REDIRECT_URI, WITHINGS_TOKEN_PATH, WITHINGS_PRIVACY_MODE, WITHINGS_CACHE, WITHINGS_CACHE_PATH, WITHINGS_NO_CACHE

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

WITHINGS_CLIENT_ID env
Withings OAuth client ID. Optional when configured with withings-mcp-server setup.
WITHINGS_CLIENT_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…

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 davidmosiah 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1026 个服务器的 0%
发布到注册中心的时间比此分类中其他 1026 个服务器的 19% 更新
基础检查结果等于或优于此分类中其他 1026 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Withingsmcp 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：WITHINGS_CLIENT_SECRET

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.7）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Langcare MCP FHIR

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

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

作者：thetahealth正在增长↓ 290/周★ 1408昨天更新

在你的电脑上运行✓ thetahealth.ai

安装

FHIR MCP Server

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

作者：wso2正在增长↓ 823/周★ 13710天前更新

在你的电脑上运行

安装

Langcare MCP FHIR

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

作者：langcare起步阶段↓ 297/周★ 709个月前更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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