Withings Claude integration over MCP
Yes. Withings can connect to Claude over MCP through AIPx's adapter for the official Withings API. Authorize your account with OAuth, then choose read tools for body measurements, activity, workouts and sleep without granting an agent device or data-editing operations.
What your agent can do with Withings
The adapter exposes five read tools: measurements, daily activity, workouts, detailed sleep and sleep summaries. Withings uses POST for some transport requests, but these operations still read data. They use the authorized user information, metrics and activity scopes. Available measurements depend on devices, sync state and regional metric support.
| Tool | What it does | Access | Mode |
|---|---|---|---|
| get_measurements | Body measurements | read | Allow |
| get_activity | Daily aggregated activity | read | Allow |
| get_workouts | Workouts | read | Allow |
| get_sleep | Detailed sleep stages | read | Allow |
| get_sleep_summary | Sleep summaries | read | Allow |
Source labels describe the checked connection. Live discovery and provider access determine availability; account-specific agent names may be normalized. Modes in this table are recommendations, not a change to upstream permissions.
Capability snapshot: 14 October 2026 · provider source
A useful trend request names the metric, date range and expected unit. Ask the agent to show the recorded values and missing dates before summarizing a change. A device that has not synced can leave a gap; the agent should not turn that gap into a zero.
Detailed sleep and daily sleep summaries answer different questions. A weekly summary may be enough for a personal planning task, while detailed stages expose more data without necessarily improving the answer. Choose the least detailed source that supports the requested comparison.
The output should describe logged trends. It cannot establish a diagnosis or prove that one behavior caused a measurement change. If two services report similar metrics differently, keep their source labels instead of silently merging them.
Withings MCP and official API options
| Route | Access method | Main difference |
|---|---|---|
| Official Withings API | Provider OAuth and API calls | Build a direct integration around defined endpoints |
| Community Withings MCP | Separate runtime and provider setup | Review implementation and credential storage |
| AIPx Withings adapter | Hosted API adapter and per-agent tools | Reuse the account alongside other approved connections |
The official Withings API reference defines data access and metrics. Schimmilab’s server and another community implementation are different routes. AIPx wraps the official API; it is not a Withings-authored MCP service.
A local server can suit users who prefer to manage health-data processing themselves. AIPx adds credential storage and request handling outside Withings in exchange for remote reuse and tool visibility controls.
Connect Withings to Claude, Claude Code, Cursor or Codex
Connect Withings through OAuth and authorize the user information, metrics and activity access requested by the adapter. No Withings password belongs in the client configuration.
- Open the AIPx dashboard, choose Withings under Integrations and complete its connection form or authorization.
- Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
- Copy the agent’s complete URL. The examples below use
AGENT_ID; replace it with the actual value from your dashboard.
An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Withings; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.
Connect Claude to Withings
In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Withings is the only service you need.
Withings MCP in Claude Code
claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_IDAuthorize through /mcp, then read a named Withings metric over an explicit date range. State units and missing records before describing trends. Claude Code MCP setup covers server and OAuth settings.
Withings MCP in Cursor
Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:
{
"mcpServers": {
"aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
}
}Sign in from Cursor and enable only the Withings reads relevant to the task. Personal measurements normally belong outside a coding workflow. See Cursor MCP setup for project versus user configuration.
Withings MCP in Codex
codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp listCodex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Withings credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.
ChatGPT can receive Withings data via custom MCP where supported, but the account’s connector access is separate from AIPx Free. Keep summaries tied to recorded values. ChatGPT MCP setup explains workspace and client conditions.
Scope Withings reads per agent
A planning assistant may need only sleep summaries and activity. A measurement analyst can have body measurements as well, while a coding agent should normally see none of this personal data. Hide tools based on the task, even though all five are reads.
The read default is Allow. That does not make broad exposure appropriate for every agent. MCP access control keeps health context out of unrelated workflows; Hide removes the tool from that agent’s callable surface.
WHOOP offers another recovery and sleep source, and Hevy supplies workout logs. Numon can provide food-diary context. Keep those sources separately labeled and combine only the data needed for a personal review.
Withings device, sync and metric limits
The API can only return data available for the authorized account. Device sync timing and regional availability can affect which metrics appear. Specify the date window and unit, and ask the agent to report missing or unsynced records.
A trend summary is an interpretation of recorded data, not a medical conclusion. Keep the source values available for review. Provider authorization and API limits remain in force, and a gateway cannot create a measurement your device never recorded.
Browse all MCP integrations to choose another connection for this agent.
The Withings connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.
What to ask your agent
Name the Withings account and a bounded task. Ask for source identifiers and a proposed result before approving a change.
FAQ
Can I connect Withings to Claude?
Yes. Connect Withings in AIPx, create an MCP agent and add its copied URL as a Claude custom connector when your account and workspace permit. Choose tools before using the connection.
How do I add Withings MCP to Claude Code?
Run claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID with your actual agent endpoint, then use /mcp to authorize and inspect tools. See Claude Code MCP setup.
Is the Withings integration free?
AIPx Free includes 3 active connected accounts and 1 agent; Pro is $3/month. Provider subscriptions, API charges and the AI client's own connector access are separate. See AIPx pricing.
Can I connect two Withings accounts?
Yes. Add separately authorized Withings connections and choose each account's tools independently for the agent. One endpoint can include both; it does not merge accounts or synchronize provider data.
Can my agent change Withings data?
No. These five Withings adapter tools read data. The connection does not expose measurement editing, device control or deletion.
When should I use the official Withings connection?
Use a direct vendor connection when one service and one client meet your needs and you prefer fewer services handling data. For an API-only service, that can mean using the official API or a compatible server you maintain. AIPx adds shared connections and agent-specific rules.