davidmosiah/google-health-mcp

Read user-authorized Google Health API v4 data — Fitbit, Pixel Watch and partners — locally via OAuth. Beta .
Local-first MCP server — tokens never leave your machine .
> ⚡ **One-command install** with Delx Wellness for Hermes:
> npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.
>
> Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.
> **What's new in 0.7.3 (2026-08-03):** headless OAuth (auth --manual) for SSH /
> containers / WSL · real-account rollup/filter fixes from external testers ·
> opt-in clinical scopes for ECG/IRN · pins live in Hermes/living-body.
> Full notes in CHANGELOG.md.
Highest-leverage contribution — real-account coverage
If you have Fitbit, Pixel Watch, Android health data or Google Health API v4
access, the most useful help is a redacted coverage report:
Review the output, remove anything you do not want public, then post the report
on issue #2 (or a
new issue). The timed proof loop on #21
closed **1/2** — see docs/proof-loop-status.md.
The command is read-only and is designed to omit OAuth secrets, local paths and raw
health measurements. A static preflight is available before OAuth with
coverage --json.
Other ways to help (no account required)
| Action | Link |
| --- | --- |
| Star if the project earned it | stargazers |
| Docs GFI — headless auth walkthrough | #22 |
| Compose with other wearables | delx-living-body |
| One-command Hermes pack | delx-wellness-hermes |
| Full registry | delx-wellness |
---
HTTP (v2 stateless)
Default is **stdio**. Optional Streamable HTTP — no session id, JSON responses, loopback only:
Env: GOOGLE_HEALTH_MCP_HOST, GOOGLE_HEALTH_MCP_PORT, GOOGLE_HEALTH_MCP_TRANSPORT=http.
Google Health MCP
**Local-first MCP server that gives your AI agent user-authorized Google Health API v4 data — Fitbit, Pixel Watch and partners — over OAuth.**
- **Install one connector** — npx -y google-health-mcp-unofficial setup
- **Run it in** Claude · Cursor · ChatGPT · Hermes · OpenClaw — see the client examples.
- **Local-first** — your tokens never leave your machine (privacy).
- **Which connector should I use?** — see the front-door guide.
> **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.
> **Unofficial project.** Not affiliated with, endorsed by or supported by Google, Fitbit or Alphabet. Not a medical device. Not medical advice.
Why this exists
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.
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.
Quickstart in 60 seconds
Create a Google Cloud OAuth client, enable the Google Health API, and add the redirect http://127.0.0.1:3000/callback. Then:
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). Full install details (scope presets, MFA, recovery) are in the Install section below.
Try it with your agent
Three things to ask first, based on tools this connector actually ships:
Tools
Start here:
- google_health_connection_status — local config, token, scope and client readiness
- google_health_data_inventory — supported domains, scopes, data type naming and agent flow
- google_health_data_type_coverage — static coverage plan, or explicit live read-only validation for issue #21
- google_health_daily_summary — daily beta summary from rollups and reconciled streams