Google Health MCP

What is Google Health MCP about?

Google Health MCP enables AI agents (Claude, Cursor, ChatGPT, Hermes, etc.) to read a user’s Google Health data such as activity, sleep, and biometric measurements from Fitbit, Pixel Watch and other partner devices. The server runs locally, keeps OAuth tokens on the user’s machine, and serves data through the Model Context Protocol (MCP) so agents never see raw credentials.

How to use Google Health MCP?

Install the connector – one‑command setup:

npx -y google-health-mcp-unofficial setup

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

Authorize the app:

npx -y google-health-mcp-unofficial auth

Verify the setup:

npx -y google-health-mcp-unofficial doctor --live

Call the tools from any MCP‑compatible client, e.g.:
- google_health_connection_status
- google_health_data_inventory
- google_health_daily_summary
- google_health_weekly_summary
- google_health_privacy_audit

Key features of Google Health MCP

Local‑first operation – tokens are stored at ~/.google-health-mcp/tokens.json with strict permissions; no secrets leave the host.
One‑command install for standalone use or via the Delx Wellness Hermes bundle.
Scope presets (basic, activity, sleep, full) simplify OAuth consent.
Privacy modes – structured (default) strips identity, GPS and secret fields; raw mode is optional for debugging.
Built‑in diagnostics – doctor, support, and coverage tools help users validate configuration and provide redacted reports for the open‑source community.
Typed tool catalog – each Google Health endpoint is exposed as an MCP tool with clear naming conventions.
Beta safety checks – read‑only validation endpoints ensure the connector works before production use.

Use cases of Google Health MCP

Personal health dashboards powered by AI agents that summarize daily/weekly activity without exposing raw tokens.
Wellness coaching bots that ask for connection status, inventory data, and generate non‑medical recommendations.
Research prototypes needing read‑only access to aggregated health data for algorithm testing.
Integration with Hermès or other AI‑assistant platforms to provide a unified health data source alongside other wellness connectors.

FAQ from the Google Health MCP

Q: Do I need a paid Google Cloud account? A: Only a standard Google Cloud project to create OAuth credentials and enable the Google Health API (free tier is sufficient for read‑only access).

Q: Is my health data sent to any third‑party server? A: No. All OAuth tokens and raw responses remain on the local machine; the MCP server only forwards sanitized data to the AI agent.

Q: Can I restrict which tools an agent can call? A: Currently there is no per‑tool RBAC; the server trusts any local caller. Future versions may add finer granularity.

Q: What platforms are supported? A: Works on any platform that can run Node.js (Windows, macOS, Linux). The connector binds to 127.0.0.1:3000 by default.

Q: How do I contribute? A: Open issues on GitHub, provide redacted coverage reports, or submit PRs. See CONTRIBUTING.md for guidelines.

Q: Is this a medical device? A: No. It is an unofficial connector for development and personal use only.

⚡ 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.5.3 (2026-07-16): endpoint-specific civil-date and date-time validation, visible partial-summary failures, and executable boundary contracts. Full notes in CHANGELOG.md.

Current OSS proof loop — real accounts wanted

Through August 12, 2026, the highest-leverage contribution is a redacted coverage report from a real Fitbit, Pixel Watch, Android or Google Health API v4 account:

npx -y google-health-mcp-unofficial coverage --live --json

Review the output, remove anything you do not want public, then post the report to issue #3. 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.

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:

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. 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:

Use google_health_connection_status to check setup, then run
google_health_data_inventory. Tell me which Google Health domains
and scopes I have authorized.

Call google_health_daily_summary for today, then google_health_weekly_summary.
Separate observed data from suggestions and stay non-medical.

Run google_health_privacy_audit, then summarize exactly what is stored
locally and what would be sent to Google on the next call.

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 #3
google_health_daily_summary — daily beta summary from rollups and reconciled streams
google_health_weekly_summary — weekly beta review
google_health_privacy_audit — what is stored locally and what is sent to Google

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.

Privacy & what runs offline

OAuth tokens are stored locally at ~/.google-health-mcp/tokens.json with 0600 permissions.
Secrets can live in ~/.google-health-mcp/config.json or GOOGLE_HEALTH_* environment variables.
Tools never return access tokens, refresh tokens or client secrets.
GOOGLE_HEALTH_PRIVACY_MODE=structured is the default; raw mode is explicit and should be used only for debugging or deep analysis.
Structured mode preserves complete upstream physiological fields and future v4 additions while removing identity, GPS and secret-bearing values.
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.
support --redacted prints a copy-paste support bundle for GitHub issues without tokens, secrets, local paths or health measurements.
support --feedback --json prints an anonymous setup-feedback bundle for beta testers and MCP client reports.
coverage --live --json prints only redacted data-type status and point-count buckets; it never includes raw Google Health payloads.

Authorization model & trust boundary

Google OAuth controls which Google account and health scopes this connector can access. It does not authorize individual MCP callers or tools. The intended deployment is one local user running one trusted MCP host; callers that can reach the same process share its tool catalog and local OAuth grant.

There is currently no per-user, per-agent, API-key or per-tool RBAC layer. The optional HTTP transport binds to 127.0.0.1 by default and must not be exposed publicly without standards-compliant MCP authentication, isolated per-user Google credentials and an explicit authorization policy. See the full authorization model.

See the full agent demo →

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?":

npx -y delx-living-body demo

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.

Beta Testers Wanted

The highest-leverage contribution right now is real setup feedback from Fitbit, Pixel Watch, Android and Google Health API v4 users.

If you can test with a real account:

Run npx -y google-health-mcp-unofficial doctor and confirm the OAuth flow is clear.
Run npx -y google-health-mcp-unofficial support --feedback --json and paste the anonymous bundle into issue #4.
Run npx -y google-health-mcp-unofficial coverage --json for the static issue #3 plan.
After OAuth, run npx -y google-health-mcp-unofficial coverage --live --json and paste the reviewed, redacted report into issue #3.
Try google_health_connection_status, google_health_data_inventory and google_health_daily_summary from your MCP client.
Open an issue for missing data types, confusing setup steps, client-specific friction or privacy concerns.
Do not paste OAuth tokens, client secrets, local paths or personal health measurements into public issues.

Useful links:

Install

Create a Google Cloud OAuth client, enable the Google Health API, and add the local redirect:

http://127.0.0.1:3000/callback

Then run:

npx -y google-health-mcp-unofficial setup --scope-preset full
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor

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.

If setup gets stuck:

npx -y google-health-mcp-unofficial doctor --fix       # repairs local config/token permissions (chmod 600 where supported)
npx -y google-health-mcp-unofficial doctor --live      # calls safe identity/profile/settings endpoints to prove the API is reachable
npx -y google-health-mcp-unofficial coverage --live --json # redacted read-only data-type coverage for issue #3
npx -y google-health-mcp-unofficial support --redacted # copy-paste support bundle, no tokens/secrets/measurements
npx -y google-health-mcp-unofficial support --feedback --json # anonymous setup feedback for issue #4

Standalone MCP config:

{
  "mcpServers": {
    "google_health": {
      "command": "npx",
      "args": ["-y", "google-health-mcp-unofficial"]
    }
  }
}

Hermes

npx -y google-health-mcp-unofficial setup --client hermes --no-auth
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor --client hermes --fix
npx -y google-health-mcp-unofficial doctor --client hermes --live
hermes mcp test google_health

After config changes, use /reload-mcp or hermes mcp test google_health. Do not restart the gateway for normal data access.

Development

git clone https://github.com/davidmosiah/google-health-mcp.git
cd google-health-mcp
npm install
npm test

Provider	Package	Repo
WHOOP	`whoop-mcp-unofficial`	whoop-mcp
Oura	`oura-mcp-unofficial`	ouramcp
Garmin	`garmin-mcp-unofficial`	garmin-mcp
Strava	`strava-mcp-unofficial`	strava-mcp
Fitbit	`fitbit-mcp-unofficial`	fitbitmcp
Withings	`withings-mcp-unofficial`	withingsmcp
Apple Health	`apple-health-mcp-unofficial`	apple-health-mcp
Polar	`polar-mcp-unofficial`	polarmcp
Nourish (nutrition)	`wellness-nourish`	wellness-nourish

📧 Contact & Support

📨 support@delx.ai — general questions, integration help, partnerships
🐛 Bug reports / feature requests — GitHub Issues
🐦 Updates — @delx369 on X
🌐 Site — wellness.delx.ai

License

MIT - see LICENSE.

Google Health MCP