Mmcp.market

Google Health MCP server

by davidmosiah·io.github.davidmosiah/google-health-mcp·v0.5.2

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Established

62 stars421 downloads/wk

Reviews

Write one

Nobody has reviewed Google Health yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Google Health tools (26, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • google_health_agent_manifest

    Machine-readable install, runtime and client guidance for AI agents. Does not call Google Health or expose secrets.

  • google_health_cache_status

    Show optional local SQLite cache status. Enable with GOOGLE_HEALTH_CACHE=sqlite or GOOGLE_HEALTH_CACHE=true.

  • google_health_capabilities

    Explain supported Google Health data, privacy boundaries, beta status and recommended agent workflow.

  • google_health_connection_status

    Check 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_daily_rollup

    Aggregate a data type over civil days using Google Health dailyRollUp. Useful for steps, distance, calories, active minutes, weight and heart summaries.

  • google_health_daily_summary

    Build a practical daily summary from Google Health rollups and reconciled streams when available. Read-only, beta, non-medical.

  • google_health_data_inventory

    Inventory supported Google Health data types, auth scopes, privacy modes and recommended first calls without calling Google APIs.

  • google_health_data_type_coverage

    Build 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_demo

    Returns 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_exchange_code

    Exchange 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_auth_url

    Generate a Google OAuth authorization URL for Google Health API. Use this first when no local token exists.

  • google_health_get_identity

    Get the Google Health identity mapping for the authenticated user. Useful for Fitbit-to-Google migrations.

  • google_health_get_profile

    Get authenticated user profile details from Google Health. Requires profile scope.

  • google_health_get_settings

    Get authenticated user settings such as units and timezone. Requires settings scope.

  • google_health_list_data_points

    Query detailed data points for a Google Health data type. Use kebab-case endpoint data types, e.g. steps, sleep, heart-rate.

  • google_health_list_data_types

    List 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_onboarding

    Return 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).

  • google_health_privacy_audit

    Return local privacy, cache, token-path and env-presence posture without revealing secret values.

  • google_health_profile_get

    Read 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_updatewrite action

    Persist 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_quickstart

    Personalized 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_reconcile_data_points

    Read a reconciled stream for one data type across sources. Supports all-sources, google-wearables and google-sources data source families.

  • google_health_revoke_access

    Revoke 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_rollup

    Aggregate a data type over physical time intervals using Google Health rollUp.

  • google_health_weekly_summary

    Build a weekly Google Health scorecard with activity, sleep, heart context and missing-data awareness. Read-only, beta, non-medical.

  • google_health_wellness_context

    Normalize Google Health activity/sleep context into the shared wellness_context shape for recommendation engines.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan75 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Google Health repository's README, as published. We do not edit it. Read it on GitHub

<!-- delx-wellness header v2 --> Google Health MCP

Read user-authorized Google Health API v4 data &mdash; Fitbit, Pixel Watch and partners &mdash; locally via OAuth. Beta. Local-first MCP server &mdash; tokens never leave your machine.

⚡ One-command install with Delx Wellness for Hermes:

npx -y delx-wellness-hermes setup &mdash; preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop &mdash; see the install section below.

What's new in 0.7.3 (2026-08-03): headless OAuth (auth --manual) for SSH /

containers / WSL · real-account rollup/filter fixes from external testers ·

opt-in clinical scopes for ECG/IRN · pins live in Hermes/living-body.

Full notes in CHANGELOG.md.

Highest-leverage contribution — real-account coverage

If you have Fitbit, Pixel Watch, Android health data or Google Health API v4 access, the most useful help is a redacted coverage report:

npx -y google-health-mcp-unofficial coverage --live --json

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y google-health-mcp-unofficial on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add google-health-mcp -- npx -y google-health-mcp-unofficial
Add to Cursor

Google Health: common questions

Is Google Health MCP server safe?
Mostly: it is graded B (83/100). Read the Google Health safety report
How do I install Google Health?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Google Health need an API key?
Yes. The registry entry asks for GOOGLE_HEALTH_CLIENT_SECRET.
Is Google Health maintained?
The last commit was 28 days ago (2026-08-29). The latest release is v0.5.2.
What can I use instead of Google Health?
Servers from other publishers that do the same job: Apple Health MCP server.

Alternatives to Google Health

Same job from other publishers: the closest match first, then the best rated.

  • Apple Health
    Local-first Apple Health MCP server for questions about your sleep, workouts and heart data.
    A

More from davidmosiah →