Skip to content
Back to search

google-health-mcp

Local-first MCP server for Google Health API v4 (Fitbit + Pixel Watch) — Claude/Cursor/Hermes

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/davidmosiah--google-health-mcp/badge.svg)](/listings/davidmosiah--google-health-mcp)

HTML

<a href="/listings/davidmosiah--google-health-mcp"><img src="/api/listings/davidmosiah--google-health-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Create a Google Cloud OAuth client, enable the Google Health API, and add the redirect `http://127.0.0.1:3000/callback`. Then:

npx -y google-health-mcp-unofficial setup --scope-preset full   # writes local config
npx -y google-health-mcp-unofficial auth                        # OAuth, tokens saved locally
npx -y google-health-mcp-unofficial doctor                      # verifies you're ready

`doctor --live` calls safe Google Health identity/profile/settings endpoints after auth to prove the API is reachable — the connection proof for this beta. That does **not** prove Claude Desktop can invoke tools: Desktop validates `outputSchema` as JSON Schema 2020-12. Use `google-health-mcp-unofficial@0.7.6+` (see [#23](https://github.com/davidmosiah/google-health-mcp/issues/23)). Full install details (scope presets, MFA, recovery) are in the [Install section](#install) below.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 380 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <!-- delx-wellness header v2 -->
  2. <h1 align="center">Google Health MCP</h1>
  3. <div align="center">
  4. <img src="assets/banner.png" alt="Google Health MCP — Google Health MCP for AI agents" width="85%" />
  5. </div>
  6. <h3 align="center">
  7. Read user-authorized Google Health API v4 data &mdash; Fitbit, Pixel Watch and partners &mdash; locally via OAuth. <strong>Beta</strong>.<br>
  8. Local-first MCP server &mdash; <strong>tokens never leave your machine</strong>.
  9. </h3>
  10. <p align="center">
  11. <a href="https://www.npmjs.com/package/google-health-mcp-unofficial"><img src="https://img.shields.io/npm/v/google-health-mcp-unofficial?style=for-the-badge&labelColor=0F172A&color=10B981&logo=npm&logoColor=white" alt="npm version" /></a>
  12. <a href="https://github.com/davidmosiah/google-health-mcp/releases/latest"><img src="https://img.shields.io/github/v/release/davidmosiah/google-health-mcp?style=for-the-badge&labelColor=0F172A&color=2563EB&logo=github" alt="GitHub release" /></a>
  13. <a href="https://www.npmjs.com/package/google-health-mcp-unofficial"><img src="https://img.shields.io/npm/dm/google-health-mcp-unofficial?style=for-the-badge&labelColor=0F172A&color=0EA5A3&logo=npm&logoColor=white" alt="npm downloads" /></a>
  14. <a href="https://github.com/davidmosiah/google-health-mcp/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/davidmosiah/google-health-mcp/ci.yml?branch=main&style=for-the-badge&labelColor=0F172A&label=CI" alt="CI" /></a>
  15. <a href="LICENSE"><img src="https://img.shields.io/badge/LICENSE-MIT-22C55E?style=for-the-badge&labelColor=0F172A" alt="License MIT" /></a>
  16. <a href="https://wellness.delx.ai/connectors/google-health"><img src="https://img.shields.io/badge/SITE-wellness.delx.ai-0EA5A3?style=for-the-badge&labelColor=0F172A" alt="Site" /></a>
  17. </p>
  18. <p align="center">
  19. <a href="https://github.com/davidmosiah/google-health-mcp/stargazers"><img src="https://img.shields.io/github/stars/davidmosiah/google-health-mcp?style=for-the-badge&labelColor=0F172A&color=FBBF24&logo=github" alt="GitHub stars" /></a>
  20. <a href="https://modelcontextprotocol.io"><img src="https://img.shields.io/badge/BUILT_FOR-MCP-7C3AED?style=for-the-badge&labelColor=0F172A" alt="Built for MCP" /></a>
  21. <a href="https://github.com/davidmosiah/delx-wellness/blob/main/docs/release-index.md"><img src="https://img.shields.io/badge/VERIFIED-release_index-0EA5A3?style=for-the-badge&labelColor=0F172A" alt="Verified release index" /></a>
  22. <a href="https://github.com/davidmosiah/delx-wellness-hermes"><img src="https://img.shields.io/badge/HERMES-one--command_setup-10B981?style=for-the-badge&labelColor=0F172A" alt="Hermes one-command setup" /></a>
  23. <a href="https://github.com/davidmosiah/delx-wellness"><img src="https://img.shields.io/badge/Google%20Health-4285F4?style=for-the-badge&labelColor=0F172A&logoColor=white" alt="Google Health" /></a>
  24. </p>
  25. > ⚡ **One-command install** with [Delx Wellness for Hermes](https://github.com/davidmosiah/delx-wellness-hermes):
  26. > `npx -y delx-wellness-hermes setup` &mdash; preconfigures this connector and the other 8 in a dedicated Hermes profile.
  27. >
  28. > Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop &mdash; see the install section below.
  29. > **What's new in 0.7.3 (2026-08-03):** headless OAuth (`auth --manual`) for SSH /
  30. > containers / WSL · real-account rollup/filter fixes from external testers ·
  31. > opt-in `clinical` scopes for ECG/IRN · pins live in Hermes/living-body.
  32. > Full notes in [CHANGELOG.md](CHANGELOG.md).
  33. ## Highest-leverage contribution — real-account coverage
  34. If you have Fitbit, Pixel Watch, Android health data or Google Health API v4
  35. access, the most useful help is a redacted coverage report:
  36. ```bash
  37. npx -y google-health-mcp-unofficial coverage --live --json
  38. ```
  39. Review the output, remove anything you do not want public, then post the report
  40. on [issue #2](https://github.com/davidmosiah/google-health-mcp/issues/2) (or a
  41. new issue). The timed proof loop on [#21](https://github.com/davidmosiah/google-health-mcp/issues/21)
  42. closed **1/2** — see [docs/proof-loop-status.md](docs/proof-loop-status.md).
  43. The command is read-only and is designed to omit OAuth secrets, local paths and raw
  44. health measurements. A static preflight is available before OAuth with
  45. `coverage --json`.
  46. ### Other ways to help (no account required)
  47. | Action | Link |
  48. | --- | --- |
  49. | Star if the project earned it | [stargazers](https://github.com/davidmosiah/google-health-mcp/stargazers) |
  50. | Docs GFI — headless auth walkthrough | [#22](https://github.com/davidmosiah/google-health-mcp/issues/22) |
  51. | Compose with other wearables | [`delx-living-body`](https://github.com/davidmosiah/delx-living-body) |
  52. | One-command Hermes pack | [`delx-wellness-hermes`](https://github.com/davidmosiah/delx-wellness-hermes) |
  53. | Full registry | [`delx-wellness`](https://github.com/davidmosiah/delx-wellness) |
  54. ---
  55. ## HTTP (v2 stateless)
  56. Default is **stdio**. Optional Streamable HTTP — no session id, JSON responses, loopback only:
  57. ```bash
  58. npx -y google-health-mcp-unofficial --http
  59. # GET http://127.0.0.1:3000/health
  60. # POST http://127.0.0.1:3000/mcp (sessionless)
  61. ```
  62. Env: `GOOGLE_HEALTH_MCP_HOST`, `GOOGLE_HEALTH_MCP_PORT`, `GOOGLE_HEALTH_MCP_TRANSPORT=http`.
  63. <!-- /delx-wellness header v2 -->
  64. # Google Health MCP
  65. **Local-first MCP server that gives your AI agent user-authorized Google Health API v4 data — Fitbit, Pixel Watch and partners — over OAuth.**
  66. - **Install one connector** — `npx -y google-health-mcp-unofficial setup`
  67. - **Run it in** Claude · Cursor · ChatGPT · Hermes · OpenClaw — see the [client examples](https://github.com/davidmosiah/delx-wellness/tree/main/examples).
  68. - **Local-first** — your tokens never leave your machine ([privacy](#privacy--what-runs-offline)).
  69. - **Which connector should I use?** — see the [front-door guide](https://github.com/davidmosiah/delx-wellness#which-connector-should-i-use).
  70. > **Beta status:** Google Health API v4 is live for builders but still evolving. Google's release notes show scope and data-type changes continuing after launch, so this connector stays in early beta and points testers to safe read-only validation paths before public production use.
  71. > **Unofficial project.** Not affiliated with, endorsed by or supported by Google, Fitbit or Alphabet. Not a medical device. Not medical advice.
  72. ## Why this exists
  73. Google Health API is the successor to Fitbit Web API: new OAuth, new base URL, v4 endpoint schema, standardized data types, reconciled streams and rollups.
  74. This MCP gives agents a clean way to discover the API, check setup, authenticate locally and query data without pasting tokens into prompts or agent configs.
  75. ## Quickstart in 60 seconds
  76. Create a Google Cloud OAuth client, enable the Google Health API, and add the redirect `http://127.0.0.1:3000/callback`. Then:
  77. ```bash
  78. npx -y google-health-mcp-unofficial setup --scope-preset full # writes local config
  79. npx -y google-health-mcp-unofficial auth # OAuth, tokens saved locally
  80. npx -y google-health-mcp-unofficial doctor # verifies you're ready
  81. ```
  82. `doctor --live` calls safe Google Health identity/profile/settings endpoints after auth to prove the API is reachable — the connection proof for this beta. That does **not** prove Claude Desktop can invoke tools: Desktop validates `outputSchema` as JSON Schema 2020-12. Use `google-health-mcp-unofficial@0.7.6+` (see [#23](https://github.com/davidmosiah/google-health-mcp/issues/23)). Full install details (scope presets, MFA, recovery) are in the [Install section](#install) below.
  83. ## Try it with your agent
  84. Three things to ask first, based on tools this connector actually ships:
  85. ```text
  86. Use google_health_connection_status to check setup, then run
  87. google_health_data_inventory. Tell me which Google Health domains
  88. and scopes I have authorized.
  89. ```
  90. ```text
  91. Call google_health_daily_summary for today, then google_health_weekly_summary.
  92. Separate observed data from suggestions and stay non-medical.
  93. ```
  94. ```text
  95. Run google_health_privacy_audit, then summarize exactly what is stored
  96. locally and what would be sent to Google on the next call.
  97. ```
  98. ## Tools
  99. Start here:
  100. - `google_health_connection_status` — local config, token, scope and client readiness
  101. - `google_health_data_inventory` — supported domains, scopes, data type naming and agent flow
  102. - `google_health_data_type_coverage` — static coverage plan, or explicit live read-only validation for issue #21
  103. - `google_health_daily_summary` — daily beta summary from rollups and reconciled streams
  104. - `google_health_weekly_summary` — weekly beta review
  105. - `google_health_privacy_audit` — what is stored locally and what is sent to Google
  106. The full tool catalog — Google Health API methods, agent manifest, diagnostics and data-type naming notes (kebab-case endpoints, snake_case filters, source families) — lives in [docs/tools.md](docs/tools.md).
  107. ## Privacy & what runs offline
  108. - OAuth tokens are stored locally at `~/.google-health-mcp/tokens.json` with `0600` permissions.
  109. - Secrets can live in `~/.google-health-mcp/config.json` or `GOOGLE_HEALTH_*` environment variables.
  110. - Tools never return access tokens, refresh tokens or client secrets.
  111. - `GOOGLE_HEALTH_PRIVACY_MODE=structured` is the default; `raw` mode is explicit and should be used only for debugging or deep analysis. An agent asking for `privacy_mode=raw` is refused unless it passes `explicit_user_intent=true`; setting `GOOGLE_HEALTH_PRIVACY_MODE=raw` yourself is your own call and needs no per-call intent.
  112. - Structured mode preserves complete upstream physiological fields and future v4 additions while removing identity, location and secret-bearing values.
  113. - "Location redaction" means a concrete key list, not a slogan. Coordinate-bearing **leaf keys**, always dropped in `structured` and `summary` (matched ignoring case, `_` and `-`, so `latitude_e7` and `latitudeE7` are the same key):
  114. <!-- gps-redacted-keys:start -->
  115. `startLatitude`, `startLongitude`, `start_latlng`, `endLatitude`, `endLongitude`, `end_latlng`, `latitude`, `longitude`, `lat`, `lon`, `lng`, `latlng`, `coordinates`, `coordinate`, `gps`, `gpx`, `geoPolylineDTO`, `map`, `polyline`, `summary_polyline`, `activities-tracker-gps`, `latitudeE7`, `longitudeE7`, `latE7`, `lngE7`, `lonE7`, `startLatitudeE7`, `startLongitudeE7`, `endLatitudeE7`, `endLongitudeE7`, `lat_deg`, `lng_deg`, `lon_deg`, `latitudeDegrees`, `longitudeDegrees`
  116. <!-- gps-redacted-keys:end -->
  117. Location **container keys**, dropped as a whole object — with their `address`/`city`/`placeId` siblings and any coordinate spelling this list never anticipated — whenever they hold a place record (an object, or an array containing objects). A container holding only scalars is a label, not a place, and survives: `location: ["gym", "home"]` stays, `location: { latitudeE7: … }` does not.
  118. <!-- gps-redacted-containers:start -->
  119. `location`, `locations`, `geoLocation`, `geoLocations`, `geo`, `geoJson`, `route`, `routes`, `position`, `positions`, `waypoint`, `waypoints`, `trackPoint`, `trackPoints`, `placeVisit`
  120. <!-- gps-redacted-containers:end -->
  121. `google_health_privacy_audit` returns both live lists in `gps_redacted_keys` and `gps_redacted_container_keys`, and `gps_redaction_default` is measured at call time by pushing a synthetic record through both non-raw modes and scanning the output by key **and by coordinate value** — it is not a hardcoded `true`. `npm run test:redaction-docs` fails the build if these two blocks stop matching the code, so the published promise cannot drift from the enforcement list again. Google Health API v4 does not currently document a location/route data type, so this is a forward-compatible guard rather than a patch for an observed leak.
  122. - Limits of that promise, stated instead of implied. Every line below is proved by a behavioural test (`npm run test:declared-limits`) that fails if the behaviour changes; a line marked **NOT VERIFIED** is a statement no test backs, labelled instead of left to read as a guarantee. A limit written here without a test fails the build:
  123. <!-- declared-limits:start -->
  124. - `default_mode_is_structured` — with no `privacy_mode` argument and no `GOOGLE_HEALTH_PRIVACY_MODE`, every read runs in `structured`.
  125. - `raw_requires_explicit_user_intent` — an agent asking for `privacy_mode=raw` is refused with `USER_ACTION_REQUIRED` unless it also passes `explicit_user_intent=true`.
  126. - `local_raw_default_needs_no_per_call_intent` — `GOOGLE_HEALTH_PRIVACY_MODE=raw` in your own config or environment is honoured on every call with no per-call intent; the gate is about agent escalation, not about the machine owner.
  127. - `raw_is_an_unfiltered_passthrough` — `raw` returns the upstream payload unchanged; redaction is a property of `structured` and `summary`, never of `raw`.
  128. - `structured_drops_identity_and_secret_keys` — tokens, `authorization`, e-mail, names and avatars are dropped at any depth in `structured`, while physiology and provenance survive.
  129. - `summary_is_never_less_restrictive_than_structured` — `summary` strips first and summarizes after, so nothing `structured` drops can reappear in `summary`.
  130. - `summary_flattens_numeric_leaves_to_depth_2` — `summary` promotes numeric leaves down to depth 2 of the data-type payload into `value`; anything deeper is not reported at all.
  131. - `summary_promotes_unlisted_coordinate_keys` — a coordinate key outside the lists above is promoted by `summary`, not hidden. The key list is the boundary, not the mode.
  132. - `altitude_and_elevation_are_not_location` — `altitude` is an official v4 data type (`activity_and_fitness`) and survives redaction, as does `elevation`; an altitude alone does not localize a user.
  133. - `altitude_inside_a_place_container_is_dropped` — the same altitude inside a redacted location container dies with the container.
  134. - `location_guard_never_observed_upstream` — NOT VERIFIED: Google Health API v4 documents no location/route data type, so no test here has ever seen a real Google payload carrying coordinates. The key list is a forward-compatible guard derived from Google's own encodings, not a measured fix for an observed leak.
  135. <!-- declared-limits:end -->
  136. - Daily rollups use validated civil `YYYY-MM-DD` ranges; general rollups preserve exact timezone-aware ISO date-times. Invalid or reversed ranges fail before HTTP.
  137. - `"today"` in summaries and daily rollups resolves in the `timezone` argument, else the wellness profile's timezone, else UTC. An invalid IANA timezone is rejected.
  138. - `support --redacted` prints a copy-paste support bundle for GitHub issues without tokens, secrets, local paths or health measurements.
  139. - `support --feedback --json` prints an anonymous setup-feedback bundle for beta testers and MCP client reports.
  140. - `coverage --live --json` prints only redacted data-type status and point-count buckets; it never includes raw Google Health payloads.
  141. ## Authorization model & trust boundary
  142. Google OAuth controls which Google account and health scopes this connector can
  143. access. It does **not** authorize individual MCP callers or tools. The intended
  144. deployment is one local user running one trusted MCP host; callers that can
  145. reach the same process share its tool catalog and local OAuth grant.
  146. There is currently no per-user, per-agent, API-key or per-tool RBAC layer. The
  147. optional HTTP transport binds to `127.0.0.1` by default and must not be exposed
  148. publicly without standards-compliant MCP authentication, isolated per-user
  149. Google credentials and an explicit authorization policy. See the full
  150. [authorization model](docs/authorization.md).
  151. ## See the full agent demo →
  152. Want to see an agent actually reason over this connector alongside the rest of the stack? The shared, reproducible demo answers the anchor question **"Should I train hard today?"**:
  153. ```bash
  154. npx -y delx-living-body demo
  155. ```
  156. `delx-living-body` composes whatever connectors it detects locally with rule-based (offline) synthesis — readiness-first and non-medical. For this connector specifically, `npx -y google-health-mcp-unofficial doctor --live` is the local proof that your Google Health auth is wired correctly.
  157. ## Beta Testers Wanted
  158. The highest-leverage contribution right now is real setup feedback from Fitbit, Pixel Watch, Android and Google Health API v4 users.
  159. If you can test with a real account:
  160. - Run `npx -y google-health-mcp-unofficial doctor` and confirm the OAuth flow is clear.
  161. - Run `npx -y google-health-mcp-unofficial support --feedback --json` and paste the anonymous bundle into issue #4.
  162. - Run `npx -y google-health-mcp-unofficial coverage --json` for the static coverage plan.
  163. - After OAuth, run `npx -y google-health-mcp-unofficial coverage --live --json` and paste the reviewed, redacted report into [issue #2](https://github.com/davidmosiah/google-health-mcp/issues/2).
  164. - Try `google_health_connection_status`, `google_health_data_inventory` and `google_health_daily_summary` from your MCP client.
  165. - Open an issue for missing data types, confusing setup steps, client-specific friction or privacy concerns.
  166. - Do **not** paste OAuth tokens, client secrets, local paths or personal health measurements into public issues.
  167. Useful links:
  168. - [Beta testers wanted](https://github.com/davidmosiah/google-health-mcp/issues/2)
  169. - [Proof loop status (honest 1/2)](docs/proof-loop-status.md)
  170. - [Beta testers / new coverage](https://github.com/davidmosiah/google-health-mcp/issues/2)
  171. - [MCP client setup feedback](https://github.com/davidmosiah/google-health-mcp/issues/4)
  172. - [Beta feedback guide](docs/beta-feedback.md)
  173. - [Data coverage harness](docs/data-coverage.md)
  174. - [Anonymous setup feedback](docs/setup-feedback.md)
  175. - [Demo](docs/demo.md)
  176. - [Discovery kit](docs/discovery.md)
  177. ## Install
  178. Create a Google Cloud OAuth client, enable the Google Health API, and add the local redirect:
  179. ```text
  180. http://127.0.0.1:3000/callback
  181. ```
  182. Then run:
  183. ```bash
  184. npx -y google-health-mcp-unofficial setup --scope-preset full
  185. npx -y google-health-mcp-unofficial auth
  186. npx -y google-health-mcp-unofficial doctor
  187. ```
  188. ### Headless hosts (servers, SSH, containers, WSL)
  189. `auth` normally opens a browser and catches the redirect on `127.0.0.1`. On a host with no
  190. browser that cannot work. When it detects a headless host — SSH, or no `DISPLAY` /
  191. `WAYLAND_DISPLAY` — it switches to pasting the redirect back in:
  192. ```bash
  193. npx -y google-health-mcp-unofficial auth --manual
  194. ```
  195. Non-interactive provisioning:
  196. ```bash
  197. npx -y google-health-mcp-unofficial auth --print-url
  198. npx -y google-health-mcp-unofficial auth --code "http://127.0.0.1:3000/callback?code=..."
  199. ```
  200. See [docs/oauth.md](docs/oauth.md) for `--local-callback`, SSH tunnel notes, and
  201. `GOOGLE_HEALTH_HEADLESS`.
  202. Scope presets keep OAuth consent easier to reason about — `basic`, `activity`, `sleep` and `full`. The full preset list, the exact read-only scope URLs and the OAuth endpoints live in [docs/oauth.md](docs/oauth.md).
  203. If setup gets stuck:
  204. ```bash
  205. npx -y google-health-mcp-unofficial doctor --fix # repairs local config/token permissions (chmod 600 where supported)
  206. npx -y google-health-mcp-unofficial doctor --live # calls safe identity/profile/settings endpoints to prove the API is reachable
  207. npx -y google-health-mcp-unofficial coverage --live --json # redacted read-only data-type coverage for issue #21
  208. npx -y google-health-mcp-unofficial support --redacted # copy-paste support bundle, no tokens/secrets/measurements
  209. npx -y google-health-mcp-unofficial support --feedback --json # anonymous setup feedback for issue #4
  210. ```
  211. Standalone MCP config:
  212. ```json
  213. {
  214. "mcpServers": {
  215. "google_health": {
  216. "command": "npx",
  217. "args": ["-y", "google-health-mcp-unofficial"]
  218. }
  219. }
  220. }
  221. ```
  222. ## Hermes
  223. ```bash
  224. npx -y google-health-mcp-unofficial setup --client hermes --no-auth
  225. npx -y google-health-mcp-unofficial auth
  226. npx -y google-health-mcp-unofficial doctor --client hermes --fix
  227. npx -y google-health-mcp-unofficial doctor --client hermes --live
  228. hermes mcp test google_health
  229. ```
  230. After config changes, use `/reload-mcp` or `hermes mcp test google_health`. Do not restart the gateway for normal data access.
  231. ## Development
  232. ```bash
  233. git clone https://github.com/davidmosiah/google-health-mcp.git
  234. cd google-health-mcp
  235. npm install
  236. npm test
  237. ```
  238. ## Links
  239. - [Changelog](CHANGELOG.md) · [Contributing](CONTRIBUTING.md) · [Security](SECURITY.md) · [Authorization model](docs/authorization.md)
  240. - Google Health API: https://developers.google.com/health
  241. - Release notes: https://developers.google.com/health/release-notes
  242. - REST reference: https://developers.google.com/health/reference/rest
  243. - Scopes: https://developers.google.com/health/scopes
  244. - Data types: https://developers.google.com/health/data-types
  245. - Migration guide: https://developers.google.com/health/migration
  246. - Delx Wellness registry: https://github.com/davidmosiah/delx-wellness
  247. <!-- delx-wellness see-also -->
  248. ## See also
  249. The full [Delx Wellness](https://wellness.delx.ai) connector library:
  250. | Provider | Package | Repo |
  251. |---|---|---|
  252. | WHOOP | [`whoop-mcp-unofficial`](https://www.npmjs.com/package/whoop-mcp-unofficial) | [whoop-mcp](https://github.com/davidmosiah/whoop-mcp) |
  253. | Oura | [`oura-mcp-unofficial`](https://www.npmjs.com/package/oura-mcp-unofficial) | [ouramcp](https://github.com/davidmosiah/ouramcp) |
  254. | Garmin | [`garmin-mcp-unofficial`](https://www.npmjs.com/package/garmin-mcp-unofficial) | [garmin-mcp](https://github.com/davidmosiah/garmin-mcp) |
  255. | Strava | [`strava-mcp-unofficial`](https://www.npmjs.com/package/strava-mcp-unofficial) | [strava-mcp](https://github.com/davidmosiah/strava-mcp) |
  256. | Fitbit | [`fitbit-mcp-unofficial`](https://www.npmjs.com/package/fitbit-mcp-unofficial) | [fitbitmcp](https://github.com/davidmosiah/fitbitmcp) |
  257. | Withings | [`withings-mcp-unofficial`](https://www.npmjs.com/package/withings-mcp-unofficial) | [withingsmcp](https://github.com/davidmosiah/withingsmcp) |
  258. | Apple Health | [`apple-health-mcp-unofficial`](https://www.npmjs.com/package/apple-health-mcp-unofficial) | [apple-health-mcp](https://github.com/davidmosiah/apple-health-mcp) |
  259. | Polar | [`polar-mcp-unofficial`](https://www.npmjs.com/package/polar-mcp-unofficial) | [polarmcp](https://github.com/davidmosiah/polarmcp) |
  260. | Nourish (nutrition) | [`wellness-nourish`](https://www.npmjs.com/package/wellness-nourish) | [wellness-nourish](https://github.com/davidmosiah/wellness-nourish) |
  261. **One-command setup for Hermes** — preconfigures every connector above plus wellness skills + onboarding: [`delx-wellness-hermes`](https://github.com/davidmosiah/delx-wellness-hermes).
  262. <!-- /delx-wellness see-also -->
  263. ## 📧 Contact & Support
  264. - 📨 **support@delx.ai** — general questions, integration help, partnerships
  265. - 🐛 **Bug reports / feature requests** — [GitHub Issues](https://github.com/davidmosiah/google-health-mcp/issues)
  266. - 🐦 **Updates** — [@delx369](https://x.com/delx369) on X
  267. - 🌐 **Site** — [wellness.delx.ai](https://wellness.delx.ai)
  268. ## License
  269. MIT - see [LICENSE](LICENSE). [Code of Conduct](CODE_OF_CONDUCT.md).
  270. > Agent-ready yardstick: [mcp-scorecard](https://github.com/davidmosiah/mcp-scorecard) — aim ≥90 on CI.
  271. ## Skill or MCP
  272. Same package, two doors. MCP registers tools on stdio/HTTP. The [skill](skill/SKILL.md) can drive the **same** tools through the CLI when the client has no MCP:
  273. ```bash
  274. npx -y google-health-mcp-unofficial call google_health_connection_status --json '{}'
  275. ```
  276. Copy `skill/SKILL.md` into your agent skills dir.
  277. ## Release migration
  278. Before upgrading to 0.8.0, review the [compatibility and migration notes](docs/migration-0.8.0.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.