🩺 google-health-mcp-server

Hand your whole-body health data to your AI — steps, distance, heart rate, and more from Apple Watch, Fitbit, or Pixel Watch, unified through Google Health.

An MCP server for the Google Health API v4 — read your daily activity, sleep, heart rate, and body metrics from any source connected to Google Health (Apple Watch import, Fitbit Air, Pixel Watch, ...) in Claude or any MCP client, and optionally sync them into an Obsidian vault.

Self-hosted and local-first: it uses your own Google Cloud OAuth app, tokens are stored on your machine at mode 0600, and no health data leaves your control.

Beta notice. The Google Health API v4 is new (public beta; legacy Fitbit Web API turns down September 2026). Field shapes may still shift. This server normalizes daily values best-effort and always returns the raw rollup points alongside, so nothing is lost if a field mapping in src/constants.ts needs a tweak against live data.

Tools

One-time setup

1. Google Cloud project + API

1. Create or pick a project at https://console.cloud.google.com/.

2. Enable the Google Health API: https://console.cloud.google.com/apis/library/health.googleapis.com

2. OAuth consent screen

1. Go to APIs & Services → OAuth consent screen. User type External.

2. Fill in the app name and your email.

3. Under Audience → Test users, add your own Google account.

4. On the Data access page, add these scopes (search "Google Health"):

   • …/auth/googlehealth.profile.readonly

   • …/auth/googlehealth.settings.readonly

   • …/auth/googlehealth.activity_and_fitness.readonly

   • …/auth/googlehealth.health_metrics_and_measurements.readonly

   • …/auth/googlehealth.sleep.readonly

   • …/auth/googlehealth.nutrition.readonly

⚠️ 7-day token caveat. While the consent screen is in Testing status, Google issues refresh tokens that expire after 7 days — the daily sync will start failing weekly and you'll need to re-run npm run oauth. To get long-lived tokens, publish the app to Production (APIs & Services → OAuth consent screen → Publish app). For your own single-user use you can click through the "unverified app" warning; full Google verification is only needed to onboard other users.

3. OAuth credentials

1. APIs & Services → Credentials → Create credentials → OAuth client ID.

2. Application type: Web application.

3. Under Authorized redirect URIs, add exactly:

   http://localhost:47813/callback

   (Must match GOOGLE_HEALTH_OAUTH_PORT. Change both together if 47813 is taken.)

4. Copy the Client ID and Client secret.

4. Configure + authorize

npm install
cp .env.example .env          # then paste your client ID + secret into .env
npm run oauth                 # opens a browser; approve access. Tokens saved to
                              # ~/.config/google-health-mcp/tokens.json (mode 0600)
npm run build

Verify it works:

node dist/index.js            # should print "Google Health MCP server running on stdio"

…or call connection_status once registered in your MCP client.

Register in Claude

Add to ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude:

{
  "mcpServers": {
    "google-health": {
      "command": "node",
      "args": ["/Users/<you>/projects/google-health-mcp-server/dist/index.js"],
      "env": {
        "GOOGLE_HEALTH_TOKENS_PATH": "/Users/<you>/.config/google-health-mcp/tokens.json",
        "OBSIDIAN_VAULT_PATH": "/Users/<you>/Documents/Obsidian Vault"
      }
    }
  }
}

The runtime reads the client ID/secret back from the tokens file, so they don't need to be in the MCP env block — only the token path and (optionally) the vault path.

Daily Obsidian sync (optional)

Set OBSIDIAN_VAULT_PATH, then either call sync_health_to_obsidian from Claude or run the CLI / a launchd cron:

npm run sync                  # incremental sync since last run

A launchd template is in launchd/. Copy it to ~/Library/LaunchAgents/, replace __USERNAME__, and launchctl bootstrap gui/$(id -u) <plist>. (Remember the 7-day token caveat above — the cron fails weekly until the OAuth app is in Production.)

Develop

npm run build       # tsc --noCheck → dist/
npm run typecheck   # strict type check (excludes tests)
npm test            # vitest — pure logic (civil-date math, value extraction)
npm run dev         # build + run the server on stdio

See CLAUDE.md for architecture notes and known pitfalls.