google-health-mcp

Google Health MCP Unofficial

Unofficial local-first MCP server for Google Health API v4.
Important tools: google_health_connection_status, google_health_data_inventory, google_health_data_type_coverage, google_health_get_identity, google_health_list_data_points, google_health_reconcile_data_points, google_health_daily_rollup, google_health_rollup, google_health_daily_summary, google_health_weekly_summary.
Privacy: tokens stay local under ~/.google-health-mcp. summary and structured modes minimize sensitive output. raw mode is explicit.
Authorization: Google OAuth scopes protect upstream data. The local MCP process does not identify or authorize individual users, agents, API keys or tools. HTTP is localhost-only by default and must not be exposed publicly without an authenticated gateway and isolated per-user Google credentials.
Boundary: beta Google Health API v4 connector. Not affiliated with Google or Fitbit. Not medical advice.
Beta tester ask: validate setup, OAuth, data type coverage and privacy boundaries with Fitbit, Pixel Watch, Android and Google Health API v4 access. Check official release notes because scopes and data types can change.
Data coverage: use `google-health-mcp-server coverage --json` for a static plan and `google-health-mcp-server coverage --live --json` only after OAuth. Live reports are read-only and omit raw payloads, health measurements, OAuth secrets and local paths.
Anonymous setup feedback: use `google-health-mcp-server support --feedback --json`; it is designed for issue #4 and omits tokens, client-secret values, local paths and health measurements.