Log inSubmit server
Withingsmcp logo

Withingsmcp

Local MCP access to Withings body, sleep, activity, workout, and heart data for AI health workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Withingsmcp

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "withingsmcp": {
      "command": "npx",
      "args": [
        "-y",
        "delx-wellness-hermes"
      ],
      "env": {
        "WITHINGS_MCP_HOST": "YOUR_VALUE_HERE",
        "WITHINGS_MCP_PORT": "YOUR_VALUE_HERE",
        "WITHINGS_MCP_TRANSPORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y delx-wellness-hermes

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

withingsmcp MCP server connects MCP-compatible agents to data from a user’s Withings account through the official Withings Public API. It handles OAuth locally, normalizes supported responses, and provides summaries plus list tools for body measures, sleep, activity, workouts, and heart records. Stdio is the default transport, with optional loopback Streamable HTTP. Reach for it when an agent needs personal Withings trends without manually copying data from the Withings app.

Use cases

  • Review today’s body, sleep, activity, and heart metrics
  • Compare this week’s health data with the previous week
  • Query historical weight and body-composition records
  • Investigate sleep changes alongside body measurements
  • List workouts and daily activity summaries

Key features

  • Local OAuth token handling
  • Daily and weekly health summaries
  • Body, activity, workout, sleep, and heart queries
  • Date filtering and result limits for body records
  • Stdio and optional loopback Streamable HTTP transports
  • Privacy and connection diagnostics

Tools10

What Withingsmcp lets your agent do. Expand a tool for its parameters.

Self-reported~212 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/10 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev ¡ delx-wellness-hermes (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads143Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed10Callable tools this server registers over MCP.

How Withingsmcp works

What withingsmcp MCP server does

The withingsmcp MCP server gives an MCP-compatible AI client access to selected data from a user’s Withings account. Supported domains include body measurements, daily activity, workouts, sleep summaries, detailed sleep records, and heart data when the account’s device and plan expose it.

Summary tools provide a current daily brief or a weekly scorecard with comparison to the previous week and a suggested plan for the following week. List tools are available when an agent needs records rather than a high-level interpretation. The project is unofficial and is intended for use with the account owner’s own data.

How it works

The withingsmcp MCP server uses the Withings Public API and performs the signed OAuth flow locally. Access tokens are saved in ~/.withings-mcp/tokens.json with 0600 permissions and are not returned by MCP tools. Privacy modes make raw upstream payloads opt-in rather than the default.

Stdio is the default transport. The package can also run a stateless Streamable HTTP endpoint on loopback, with a health route at /health and an MCP route at /mcp. HTTP mode does not use a session ID. The server converts date filters into the formats expected by different Withings API endpoints and limits returned body-measure records with limit.

Setup and configuration

Create a Withings app in the Withings OAuth dashboard and set its redirect URI to http://127.0.0.1:3000/callback. Run the interactive setup command to provide the client ID and secret, then run the authentication command to authorize the account in a browser. The doctor command checks whether the local configuration is ready.

The recommended OAuth scopes are user.activity and user.metrics. After authentication, add the package as an MCP server using an npx command and the withings-mcp-unofficial package name. Claude Desktop users can run the client-specific setup command to write the configuration. OAuth authorization codes expire quickly, so the browser approval should be followed promptly by code exchange.

For HTTP mode, run the package with --http. WITHINGS_MCP_HOST, WITHINGS_MCP_PORT, and WITHINGS_MCP_TRANSPORT=http configure the HTTP listener and transport.

Tools and capabilities

The withingsmcp MCP server includes:

  • Connection and inventory checks that confirm local setup and describe supported domains, scopes, privacy modes, and suggested initial calls without contacting Withings.
  • Daily and weekly summaries covering body, sleep, activity, and available heart information.
  • Body-measure queries for weight and composition records, with after, before, and limit controls.
  • Activity and workout queries for daily summaries and logged exercise.
  • Sleep summary queries with duration, stages, efficiency, and heart-rate fields, plus detailed sleep records.
  • Heart-record queries when the connected device and plan support them.

Additional diagnostics and account tools cover capabilities, the agent manifest, privacy auditing, cache status, authorization URL generation, code exchange, and access revocation.

Limitations and notes

Available data depends on the granted scopes, connected devices, Withings plan, and the behavior of the official API. Body measures and heart records use the user.metrics scope; activity, workouts, and sleep use user.activity. Detailed sleep data is available only when the device exposes it, and heart data varies by device and plan.

The API does not expose continuous sensor telemetry. Records described as raw are upstream Withings JSON for supported endpoints, not direct device sensor streams. The project is not affiliated with, endorsed by, or supported by Withings, and use must follow the Withings Public API terms.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Withingsmcp

withingsmcp is an MCP server that connects AI agents to a user’s Withings account through the Withings Public API. Its main tools provide connection checks, data inventories, daily and weekly summaries, and queries for body measures, heart records, activity, workouts, and sleep data.

Install it through `npx` and run its setup and authentication commands. Use `npx -y withings-mcp-unofficial setup`, then `npx -y withings-mcp-unofficial auth` and `doctor`; afterward, add `npx -y withings-mcp-unofficial` to the MCP client configuration.

Yes, withingsmcp can be wired into Cursor as an MCP server. Add the package command and arguments to Cursor’s MCP configuration after completing the Withings setup and OAuth authorization steps.

It can access body measures, daily activity, workouts, sleep summaries, detailed sleep records, and supported heart records. Availability depends on OAuth scopes, device capabilities, and the Withings plan; continuous sensor telemetry is not exposed by the public API.

Related MCP servers

All in Sports All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWithingsmcp AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/withingsmcp?style=directory)](https://allmcps.com/mcp/withingsmcp)
HTML Embed
<a href="https://allmcps.com/mcp/withingsmcp"><img src="https://allmcps.com/api/badge/withingsmcp?style=directory" alt="Withingsmcp on AllMCPs" /></a>