---
title: Google Health MCP connector
description: Google Health API v4 beta connector for Fitbit, Pixel Watch and unified health data.
canonical: https://wellness.delx.ai/connectors/google-health
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Google Health MCP Connector

A local-first Google Health MCP connector that helps agents test the new Google Health API v4 without pasting Google OAuth tokens or health data into chat.

## Install

```bash
npx -y google-health-mcp-unofficial setup
npx -y google-health-mcp-unofficial doctor
```

## Agent client config

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

## Signals

- Google Health API v4
- Fitbit Migration
- Steps
- Sleep
- Heart
- Rollups

## Data availability

- Identity, profile and settings: available. Uses users.getIdentity, users.getProfile and users.getSettings through Google Health API v4.
- Steps, activity, calories and distance: available. Available through supported data types and granted activity scopes.
- Sleep, heart rate, HRV, SpO2 and weight: conditional. Depends on supported devices, account data, data type support and granted scopes.
- Reconciled streams: available. Uses the API reconcile endpoint to query a single stream across sources where supported.
- Daily and physical-time rollups: available. Uses dailyRollUp and rollUp for supported data types.
- Writes, deletes, webhooks and TCX export: not_available. The public connector is intentionally read-only for the beta launch.
- Continuous live device telemetry: not_available. Not exposed as a live sensor stream by this MCP.

## MCP tools

### Start here

- `google_health_connection_status`
- `google_health_data_inventory`
- `google_health_daily_summary`
- `google_health_weekly_summary`

### Auth and diagnostics

- `google_health_capabilities`
- `google_health_agent_manifest`
- `google_health_privacy_audit`
- `google_health_cache_status`
- `google_health_get_auth_url`
- `google_health_exchange_code`
- `google_health_revoke_access`

### Identity and settings

- `google_health_get_identity`
- `google_health_get_profile`
- `google_health_get_settings`

### Data points

- `google_health_list_data_points`
- `google_health_reconcile_data_points`

### Rollups and context

- `google_health_daily_rollup`
- `google_health_rollup`
- `google_health_wellness_context`

## Prompts

- `google_health_daily_checkin`
- `google_health_weekly_review`
- `google_health_data_type_investigation`

## Resources

- `google-health://inventory`
- `google-health://capabilities`
- `google-health://agent-manifest`
- `google-health://profile`
- `google-health://latest/steps`
- `google-health://summary/daily`
- `google-health://summary/weekly`

## Privacy

- Google OAuth tokens stay local under ~/.google-health-mcp.
- The MCP client never receives access tokens, refresh tokens or client secrets.
- The default privacy mode is structured, with raw upstream JSON only by explicit request.
- The connector is read-only while the Google Health API v4 launch window is still moving.

## Best for

- Fitbit Web API migration testing
- Pixel Watch wellness summaries
- Google Health API data type discovery
- Daily and weekly agent check-ins

## Known limits

- Google documents possible breaking changes until the end of May 2026.
- Requires a Google Cloud OAuth client and user consent.
- Data availability depends on Google Health API support, account data and granted scopes.
- Not affiliated with Google, Fitbit or Alphabet.

## Links

- GitHub: https://github.com/davidmosiah/google-health-mcp
- npm: https://www.npmjs.com/package/google-health-mcp-unofficial
- Provider docs: https://developers.google.com/health