Koskamo

Withings Health Data MCP

A remote MCP server that connects Withings health devices to AI assistants like Claude and ChatGPT. It provides read-only access to sleep, body, activity, and heart metrics via OAuth 2.0, allowing users to ask natural language questions about their health data without exporting spreadsheets.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Withings Health Data MCP logo, by akutishevskyCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-07Published by akutishevsky
You need:OAuth 2.0 + PKCEAvailable on all Claude plans (Free accounts are limited to one custom connector)Requires a ChatGPT Plus, Pro, Business, Enterprise, or Edu plan (web)Business/Enterprise admins must allow developer mode first
MCP endpoint (Streamable HTTP)
https://withings-mcp.com/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Analyze sleep stages, duration, and heart rate variability
  • Track weight trends and body composition metrics
  • Review workout data including steps and calories burned
  • Access ECG recordings and atrial fibrillation detection results

Source and maintenance

Community listingRegistry 1.3.0
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
410 ms
95th percentile latency
410 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 410 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http withings-health-data-mcp https://withings-mcp.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add withings-health-data-mcp --url https://withings-mcp.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable withings-health-data-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "withings-health-data-mcp": {
      "url": "https://withings-mcp.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "withings-health-data-mcp": {
      "type": "streamableHttp",
      "url": "https://withings-mcp.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start withings-health-data-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "withings-health-data-mcp": {
      "type": "http",
      "url": "https://withings-mcp.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http withings-health-data-mcp https://withings-mcp.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://withings-mcp.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "withings-health-data-mcp": {
      "serverUrl": "https://withings-mcp.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Withings Health Data MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.