MCP Tools DirectoryAbout this integration
MCP server for the Withings Health API with OAuth, local SQLite cache, and trend analysis.
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.8.0
- Package
- withings-mcp
- Last compatibility test
- Not independently tested
Connect your agent
withings-mcpPublisher documentation reviewed offline; the package and Withings API were not executed. Setup requires a registered Withings application, client ID and secret, and interactive browser authorization. Health data and OAuth tokens remain sensitive local data governed by the user's account permissions.
Capabilities: Health-data synchronization, Cached body, sleep, activity, and workout queries, Live ECG and device queries, Health trend analysis
Connected profiles
Additional details
io.github.partymola/withings-mcp
Source ↗ · Checked 2026-09-170.8.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17withings-mcp
Source ↗ · Checked 2026-09-190.8.0
Source ↗ · Checked 2026-09-19The publisher documents a stdio MCP server with automatic token refresh and cache-backed queries after setup.
Source ↗ · Checked 2026-09-19Requires a registered Withings application with client ID and secret followed by interactive browser OAuth authorization; tokens are saved locally.
Source ↗ · Checked 2026-09-19After authorization, configure the MCP client to spawn the withings-mcp console script over stdio; optional variables select the credential and SQLite paths.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19