Withings MCP Server

Withings MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Withings MCP directly instead of describing what you should do. MCP server for Withings health data integration.

What you get

A Model Context Protocol (MCP) server that brings your Withings health data into Claude. Access your sleep patterns, body measurements, workouts, heart data, and more through natural conversation.

What the assistant can call

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

• Prerequisites — The Prerequisites tool exposed by this server

Configuration and credentials

You will need 5 environment variables: SUPABASE_URL, SUPABASE_SECRET_KEY, WITHINGS_CLIENT_ID, WITHINGS_CLIENT_SECRET, ENCRYPTION_SECRET. 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.

1. A Withings account with connected devices 2. Claude Desktop or any other MCP-compatible client installed on your computer

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Withings MCP's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by akutishevsky; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• 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 withings mcp mcp server does with a few real requests.