Skip to main content
Glama

⚡ Instalación con un comando con Delx Wellness para Hermes: npx -y delx-wellness-hermes setup — preconfigura este conector y los otros 8 en un perfil dedicado de Hermes.

O conéctalo de forma independiente en Claude Desktop / Cursor / ChatGPT Desktop — consulta la sección de instalación a continuación.


Servidor MCP no oficial y local-first para la nueva API v4 de Google Health.

Permite que Claude, Cursor, Hermes, OpenClaw y otros clientes MCP lean datos de Google Health autorizados por el usuario desde Fitbit, Pixel Watch y fuentes de terceros compatibles a través del flujo OAuth 2.0 de Google.

Estado Beta: Google recomienda esperar hasta finales de mayo de 2026 antes de lanzar oficialmente las integraciones de la API de Google Health, ya que pueden producirse cambios importantes mientras se incorpora la opinión de los desarrolladores. Este conector se publica intencionadamente como una versión beta temprana para los desarrolladores que quieran probar la API ahora.

Proyecto no oficial. No está afiliado, respaldado ni apoyado por Google, Fitbit o Alphabet. No es un dispositivo médico. No es un consejo médico.

Se buscan probadores beta

La contribución de mayor impacto en este momento es la retroalimentación real de la configuración por parte de usuarios de Fitbit, Pixel Watch, Android y la API v4 de Google Health.

Si puedes probar con una cuenta real:

  • Ejecuta npx -y google-health-mcp-unofficial doctor y confirma que el flujo de OAuth es claro.

  • Prueba google_health_connection_status, google_health_data_inventory y google_health_daily_summary desde tu cliente MCP.

  • Abre un issue para tipos de datos faltantes, pasos de configuración confusos, fricción específica del cliente o preocupaciones de privacidad.

  • No pegues tokens de OAuth, secretos de cliente o mediciones de salud personales en issues públicos.

Enlaces útiles:

Related MCP server: google-health-mcp-server

Por qué existe esto

La API de Google Health es la sucesora de la API web de Fitbit: nuevo OAuth, nueva URL base, esquema de endpoint v4, tipos de datos estandarizados, flujos reconciliados y resúmenes.

Este MCP ofrece a los agentes una forma limpia de descubrir la API, verificar la configuración, autenticarse localmente y consultar datos sin pegar tokens en prompts o configuraciones de agentes.

Demo de 30 segundos

npx -y google-health-mcp-unofficial setup
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor

Luego inicia tu agente con:

  • google_health_connection_status

  • google_health_data_inventory

  • google_health_privacy_audit

  • google_health_daily_summary

Instalación

Crea un cliente OAuth de Google Cloud, habilita la API de Google Health y añade:

http://127.0.0.1:3000/callback

Luego ejecuta:

npx -y google-health-mcp-unofficial setup
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor

Scopes de solo lectura recomendados:

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

Configuración de MCP independiente:

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

Herramientas

Empieza aquí:

  • google_health_connection_status - configuración local, token, scope y preparación del cliente

  • google_health_data_inventory - dominios compatibles, scopes, nomenclatura de tipos de datos y flujo del agente

  • google_health_agent_manifest - guía de instalación/ejecución legible por máquina

  • google_health_daily_summary - resumen diario beta de resúmenes y flujos reconciliados

  • google_health_weekly_summary - revisión semanal beta

Métodos de la API de Google Health:

  • google_health_get_identity

  • google_health_get_profile

  • google_health_get_settings

  • google_health_list_data_points

  • google_health_reconcile_data_points

  • google_health_daily_rollup

  • google_health_rollup

Diagnóstico:

  • google_health_get_auth_url

  • google_health_exchange_code

  • google_health_privacy_audit

  • google_health_cache_status

  • google_health_revoke_access

  • google_health_wellness_context

Notas sobre tipos de datos

Las rutas de los endpoints usan kebab case:

steps
sleep
heart-rate
daily-resting-heart-rate
daily-heart-rate-variability
active-zone-minutes
total-calories
weight
exercise

Las expresiones de filtro usan snake case:

steps.interval.civil_start_time >= "2026-05-07"
heart_rate.sample_time.physical_time >= "2026-05-07T00:00:00Z"
sleep.interval.civil_start_time >= "2026-05-07"

Familias de fuentes compatibles con la API:

users/me/dataSourceFamilies/all-sources
users/me/dataSourceFamilies/google-wearables
users/me/dataSourceFamilies/google-sources

Privacidad

  • Los tokens de OAuth se almacenan localmente en ~/.google-health-mcp/tokens.json con permisos 0600.

  • Los secretos pueden vivir en ~/.google-health-mcp/config.json o en variables de entorno GOOGLE_HEALTH_*.

  • Las herramientas nunca devuelven tokens de acceso, tokens de actualización o secretos de cliente.

  • GOOGLE_HEALTH_PRIVACY_MODE=structured es el valor predeterminado.

  • El modo raw es explícito y debe usarse solo para depuración o análisis profundo.

Hermes

npx -y google-health-mcp-unofficial setup --client hermes --no-auth
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor --client hermes
hermes mcp test google_health

Después de los cambios de configuración, usa /reload-mcp o hermes mcp test google_health. No reinicies la puerta de enlace para el acceso normal a los datos.

Desarrollo

git clone https://github.com/davidmosiah/google-health-mcp.git
cd google-health-mcp
npm install
npm test

Enlaces

Licencia

MIT - ver LICENSE.

Available Tools

26 tools
google_health_agent_manifestGoogle Health Agent ManifestA
Read-onlyIdempotent

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

Inputs: client, response_format. Returns: links, oauth, client, hermes, +12 more

google_health_cache_statusGoogle Health Cache StatusA
Read-onlyIdempotent

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

Inputs: response_format. Returns: path, enabled, entries, http_cache, +1 more

google_health_capabilitiesGoogle Health MCP CapabilitiesB
Read-onlyIdempotent

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

Inputs: response_format. Returns: links, status, creator, project, +11 more

google_health_connection_statusGoogle Health Connection StatusA
Read-onlyIdempotent

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.

Inputs: client, response_format. Returns: ok, node, cache, oauth, +12 more

google_health_daily_rollupGoogle Health Daily RollupB
Read-onlyIdempotent

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

Inputs: end_date, data_type, page_size, page_token, +6 more. Returns: data, endpoint, privacy_mode

google_health_daily_summaryGoogle Health Daily SummaryB
Read-onlyIdempotent

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

Inputs: date, timezone, response_format. Returns: kind, generated_at

google_health_data_inventoryGoogle Health Data InventoryA
Read-onlyIdempotent

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

Inputs: response_format. Returns: auth, kind, links, notes, +12 more

google_health_data_type_coverageGoogle Health Data Type CoverageA
Read-onlyIdempotent

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.

Inputs: date, live, data_types, response_format, +1 more. Returns: kind, mode

google_health_demoGoogle Health DemoA
Read-onlyIdempotent

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.

Inputs: response_format.

google_health_exchange_codeExchange Google Health OAuth CodeA

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.

Inputs: code (required), code_verifier (required), response_format. Returns: ok, note, scope, expires_at, +1 more

google_health_get_auth_urlGet Google Health OAuth URLA
Read-onlyIdempotent

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

Inputs: state, scopes, response_format. Returns: scopes, auth_url, next_step, redirect_uri, +1 more

google_health_get_identityGet Google Health IdentityA
Read-onlyIdempotent

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

Inputs: privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode

google_health_get_profileGet Google Health ProfileA
Read-onlyIdempotent

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

Inputs: privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode

google_health_get_settingsGet Google Health SettingsA
Read-onlyIdempotent

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

Inputs: privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode

google_health_list_data_pointsList Google Health Data PointsC
Read-onlyIdempotent

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

Inputs: filter, data_type, page_size, page_token, +3 more. Returns: data, endpoint, privacy_mode

google_health_list_data_typesList Google Health Data TypesA
Read-onlyIdempotent

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.

Inputs: response_format. Returns: kind, note, count, source, +3 more

google_health_onboardingDelx Wellness Onboarding FlowA
Read-onlyIdempotent

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

Inputs: locale, response_format.

google_health_privacy_auditGoogle Health Privacy AuditA
Read-onlyIdempotent

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

Inputs: response_format. Returns: notes, project, cache_path, token_path, +15 more

google_health_profile_getGet Delx Wellness ProfileA
Read-onlyIdempotent

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.

Inputs: response_format.

google_health_profile_updateUpdate Delx Wellness ProfileA

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.

Inputs: patch (required), response_format, explicit_user_intent.

google_health_quickstartGoogle Health QuickstartA
Read-onlyIdempotent

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?'

Inputs: response_format.

google_health_reconcile_data_pointsReconcile Google Health Data PointsB
Read-onlyIdempotent

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

Inputs: filter, data_type, page_size, page_token, +4 more. Returns: data, endpoint, privacy_mode

google_health_revoke_accessRevoke Google Health OAuth AccessA
Destructive

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.

Inputs: response_format, explicit_user_intent. Returns: ok, note, token_path, local_tokens_cleared

google_health_rollupGoogle Health Physical-Time RollupC
Read-onlyIdempotent

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

Inputs: end_time (required), start_time (required), data_type, page_size, +6 more. Returns: data, endpoint, privacy_mode

google_health_weekly_summaryGoogle Health Weekly ReviewA
Read-onlyIdempotent

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

Inputs: days, timezone, compare_days, response_format. Returns: kind, generated_at

google_health_wellness_contextGoogle Health Wellness ContextB
Read-onlyIdempotent

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

Inputs: days, notes, soreness, timezone, +2 more. Returns: notes, source, soreness, generated_at, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation2/5

    Multiple tools overlap in purpose: connection_status, privacy_audit, and cache_status all touch local config/cache/token readiness; data_inventory, list_data_types, data_type_coverage, and capabilities all describe supported data types/scopes. The get_profile vs profile_get pair is especially easy to confuse because one is a Google Health profile and the other is a local Delx wellness profile.

    Naming Consistency3/5

    All tools share the google_health_ prefix and use snake_case, but beyond that the pattern is mixed: verb-first names (get_profile, list_data_points, revoke_access) coexist with noun-first names (profile_get, profile_update) and pure noun names (capabilities, quickstart, data_inventory). This is readable but not a consistent verb_noun convention.

    Tool Count2/5

    At 26 tools, the server crosses the threshold where the set becomes heavy. Many tools are narrow status/help/metadata endpoints (cache_status, privacy_audit, capabilities, agent_manifest, quickstart, demo) that could reasonably be consolidated into fewer, broader tools without losing capability.

    Completeness4/5

    The tool surface covers the main lifecycle for this domain: OAuth setup, identity/profile/settings reads, data type discovery, data point listing, reconciliation, rollups, summaries, local profile persistence, and access revocation. Minor gaps exist (e.g., no explicit token-refresh tool, no update for Google Health settings), but they are unlikely to block the core read-only Google Health workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted MCP server that aggregates personal health data from Google Health, Oura, and Withings into a single, provider-attributed interface with configurable source of truth preferences.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A local-first, model-agnostic MCP server that stores personal health data in a SQLite file and provides analysis-ready views for any AI client to log, retrieve, and reason over health records.
      79
      MIT