All servers / Health / Google Health MCP server
Google Health MCP server
Unofficial local-first Google Health API v4 MCP server for AI health, sleep and activity agents.
Tested by ConnectATDScore 82 out of 100. Tested 2026-11-19 on package version 0.8.0. Package: google-health-mcp-unofficial · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 16 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.8 seconds including download)
- Tools offered: 26
- Last published: 2026-11-05
- Weekly downloads (npm): 775
- License: MIT · Direct dependencies: 6
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
google_health_data_inventory0 of 1 parameter describedInventory supported Google Health data types, auth scopes, privacy modes and recommended first calls without calling Google APIs.
google_health_list_data_types0 of 1 parameter describedList the canonical kebab-case data_type slugs accepted by the data point, reconcile and rollup tools, with each slug's unit, OAuth scope family, and which endpoint verbs (list/reconcile/rollup) support it. Call this before list_data_points, reconcile_data_points, daily_rollup or rollup to choose a valid data_type instead of guessing a slug. Static metadata; does not call Google APIs.
google_health_data_type_coverage2 of 5 parameters describedBuild a data-type coverage plan from the official Google Health API data-type table, or run explicit live read-only checks against a real OAuth account. Live mode returns only redacted status and point-count buckets, never raw health payloads.
google_health_agent_manifest0 of 2 parameters describedMachine-readable install, runtime and client guidance for AI agents. Does not call Google Health or expose secrets.
google_health_capabilities0 of 1 parameter describedExplain supported Google Health data, privacy boundaries, beta status and recommended agent workflow.
google_health_quickstart0 of 1 parameter describedPersonalized 3-step setup walkthrough for the human user. Adapts to current state (env vars set? token present? what's next?). Call this first when the user asks 'how do I connect Google Health?'
google_health_demo0 of 1 parameter describedReturns realistic Pixel-Watch-style example payloads of google_health_daily_summary, google_health_wellness_context, and google_health_daily_rollup so agents see the contract before calling real Google Health APIs.
google_health_get_auth_url2 of 3 parameters describedGenerate a Google OAuth authorization URL for Google Health API. Use this first when no local token exists.
google_health_exchange_code2 of 3 parameters describedExchange a Google OAuth authorization code for local tokens. Tokens are stored locally with 0600 permissions and are never returned. Gated: requires explicit user intent — agents must not call this autonomously.
google_health_get_identity2 of 3 parameters describedGet the Google Health identity mapping for the authenticated user. Useful for Fitbit-to-Google migrations.
google_health_get_profile2 of 3 parameters describedGet authenticated user profile details from Google Health. Requires profile scope.
google_health_get_settings2 of 3 parameters describedGet authenticated user settings such as units and timezone. Requires settings scope.
google_health_list_data_points4 of 7 parameters describedQuery detailed data points for a Google Health data type. Use kebab-case endpoint data types, e.g. steps, sleep, heart-rate.
google_health_reconcile_data_points4 of 8 parameters describedRead a reconciled stream for one data type across sources. Supports all-sources, google-wearables and google-sources data source families.
google_health_daily_rollup6 of 11 parameters describedAggregate a data type over civil days using Google Health dailyRollUp. Useful for steps, distance, calories, active minutes, weight and heart summaries.
google_health_rollup6 of 10 parameters describedAggregate a data type over physical time intervals using Google Health rollUp.
google_health_connection_status0 of 2 parameters describedCheck local Google Health config, token file, Node version, privacy mode, cache readiness and optional MCP client readiness without calling Google APIs or exposing secrets.
google_health_cache_status0 of 1 parameter describedReport disabled authenticated payload caching and retained configuration. Existing SQLite entries are preserved and not inspected.
google_health_privacy_audit0 of 1 parameter describedReturn local privacy, cache, token-path and env-presence posture without revealing secret values.
google_health_revoke_access1 of 2 parameters describedRevoke the current Google OAuth grant and delete the local token file. Use only when the user explicitly wants to disconnect Google Health. Gated: requires explicit user intent — agents must not call this autonomously.
google_health_daily_summary1 of 3 parameters describedBuild a practical daily summary from Google Health rollups and reconciled streams when available. Read-only, beta, non-medical.
google_health_weekly_summary3 of 4 parameters describedBuild a weekly Google Health scorecard with activity, sleep, heart context and missing-data awareness. Read-only, beta, non-medical.
google_health_wellness_context2 of 6 parameters describedNormalize Google Health activity/sleep context into the shared wellness_context shape for recommendation engines.
google_health_profile_get0 of 1 parameter describedRead the shared Delx Wellness profile from ~/.delx-wellness/profile.json. Returns preferred name, goals, devices, training/nutrition/exercise/agent preferences and safety flags. NEVER contains OAuth tokens or API secrets. Read-only.
google_health_profile_update2 of 3 parameters describedPersist a partial patch to ~/.delx-wellness/profile.json. Requires explicit_user_intent=true (otherwise returns USER_ACTION_REQUIRED). Rejects secret-like fields (oauth, token, secret, password, cookie, refresh, api_key, session) at write time. Use to record preferred name, goals, devices, training context, nutrition context, exercise preferences, agent preferences, and safety flags.
google_health_onboarding1 of 2 parameters describedReturn the 11-question onboarding flow plus the current profile state and missing fields. Read-only — does NOT persist anything. Pair with google_health_profile_update once the user answers. Cross-connector: the same profile is shared by every Delx Wellness MCP (whoop, garmin, oura, fitbit, strava, polar, withings, apple-health, samsung-health, google-health, nourish, cycle-coach, cgm, air).
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.