Delx Wellness
All connectors
Google

google-health-mcp-unofficial

Google Health

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.

Google Health API v4Fitbit MigrationStepsSleepHeartRollups
Install from npmRepository
Athletes training with circular smartwatches and floating teal weekly-rollup, activity, recovery and v4 API dashboards — Google Health connector context
Google OAuth 2.0

Best for builders migrating Fitbit integrations, Pixel Watch users, and early Google Health API testers who want an agent-ready local OAuth workflow.

Quick Start

terminal
npx -y google-health-mcp-unofficial setup
npx -y google-health-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "google_health": {
      "command": "npx",
      "args": ["-y", "google-health-mcp-unofficial"]
    }
  }
}
  1. 01

    Create a Google Cloud OAuth client and enable the Google Health API.

  2. 02

    Use redirect URI http://127.0.0.1:3000/callback.

  3. 03

    Run setup, auth and doctor before connecting an agent.

Recommended scopes

https://www.googleapis.com/auth/googlehealth.profile.readonly https://www.googleapis.com/auth/googlehealth.settings.readonly https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly https://www.googleapis.com/auth/googlehealth.health_metrics_and_measurements.readonly https://www.googleapis.com/auth/googlehealth.sleep.readonly https://www.googleapis.com/auth/googlehealth.nutrition.readonly

Data Availability

Available

Identity, profile and settings

Uses users.getIdentity, users.getProfile and users.getSettings through Google Health API v4.

Available

Steps, activity, calories and distance

Available through supported data types and granted activity scopes.

Conditional

Sleep, heart rate, HRV, SpO2 and weight

Depends on supported devices, account data, data type support and granted scopes.

Available

Reconciled streams

Uses the API reconcile endpoint to query a single stream across sources where supported.

Available

Daily and physical-time rollups

Uses dailyRollUp and rollUp for supported data types.

Not exposed

Writes, deletes, webhooks and TCX export

The public connector is intentionally read-only for the beta launch.

Not exposed

Continuous live device telemetry

Not exposed as a live sensor stream by this MCP.

Agent 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 and Resources

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 Model

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.