Skip to main content
Glama

⚡ Delx Wellness for Hermes를 통한 원클릭 설치: npx -y delx-wellness-hermes setup — 이 커넥터와 다른 8개의 커넥터를 전용 Hermes 프로필에 미리 구성합니다.

또는 Claude Desktop / Cursor / ChatGPT Desktop에 독립형으로 연결하세요. 아래 설치 섹션을 참조하세요.


새로운 Google Health API v4를 위한 비공식 로컬 우선 MCP 서버입니다.

이 서버를 통해 Claude, Cursor, Hermes, OpenClaw 및 기타 MCP 클라이언트는 Google의 OAuth 2.0 흐름을 통해 Fitbit, Pixel Watch 및 지원되는 타사 소스에서 사용자가 승인한 Google Health 데이터를 읽을 수 있습니다.

베타 상태: Google은 개발자 피드백을 반영하는 과정에서 변경 사항이 발생할 수 있으므로 2026년 5월 말까지는 Google Health API 통합을 공식적으로 시작하지 않을 것을 권장합니다. 이 커넥터는 지금 API를 테스트하려는 빌더를 위해 의도적으로 초기 베타 버전으로 공개되었습니다.

비공식 프로젝트. Google, Fitbit 또는 Alphabet과 제휴, 보증 또는 지원을 받지 않습니다. 의료 기기가 아니며 의학적 조언을 제공하지 않습니다.

베타 테스터 모집

현재 가장 큰 도움이 되는 기여는 Fitbit, Pixel Watch, Android 및 Google Health API v4 사용자의 실제 설정 피드백입니다.

실제 계정으로 테스트할 수 있는 경우:

  • npx -y google-health-mcp-unofficial doctor를 실행하여 OAuth 흐름이 명확한지 확인하세요.

  • MCP 클라이언트에서 google_health_connection_status, google_health_data_inventory 및 google_health_daily_summary를 시도해 보세요.

  • 누락된 데이터 유형, 혼란스러운 설정 단계, 클라이언트별 문제 또는 개인정보 보호 문제에 대해 이슈를 제기해 주세요.

  • OAuth 토큰, 클라이언트 비밀 키 또는 개인 건강 측정값을 공개 이슈에 붙여넣지 마십시오.

유용한 링크:

Related MCP server: google-health-mcp-server

이 프로젝트의 존재 이유

Google Health API는 Fitbit Web API의 후속 버전으로, 새로운 OAuth, 새로운 기본 URL, v4 엔드포인트 스키마, 표준화된 데이터 유형, 조정된 스트림 및 롤업을 제공합니다.

이 MCP는 에이전트가 API를 검색하고, 설정을 확인하고, 로컬에서 인증하고, 토큰을 프롬프트나 에이전트 구성에 붙여넣지 않고도 데이터를 쿼리할 수 있는 깔끔한 방법을 제공합니다.

30초 데모

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

그런 다음 에이전트를 다음과 같이 시작하세요:

  • google_health_connection_status

  • google_health_data_inventory

  • google_health_privacy_audit

  • google_health_daily_summary

설치

Google Cloud OAuth 클라이언트를 만들고 Google Health API를 활성화한 후 다음을 추가하세요:

http://127.0.0.1:3000/callback

그런 다음 실행하세요:

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

권장되는 읽기 전용 범위:

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

독립형 MCP 구성:

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

도구

여기서 시작하세요:

  • google_health_connection_status - 로컬 구성, 토큰, 범위 및 클라이언트 준비 상태

  • google_health_data_inventory - 지원되는 도메인, 범위, 데이터 유형 명명 및 에이전트 흐름

  • google_health_agent_manifest - 기계 판독 가능한 설치/런타임 가이드

  • google_health_daily_summary - 롤업 및 조정된 스트림의 일일 베타 요약

  • google_health_weekly_summary - 주간 베타 검토

Google Health API 메서드:

  • 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

진단:

  • 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

데이터 유형 참고 사항

엔드포인트 경로는 케밥 케이스(kebab case)를 사용합니다:

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

필터 표현식은 스네이크 케이스(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"

API에서 지원하는 소스 제품군:

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

개인정보 보호

  • OAuth 토큰은 0600 권한으로 ~/.google-health-mcp/tokens.json에 로컬로 저장됩니다.

  • 비밀 키는 ~/.google-health-mcp/config.json 또는 GOOGLE_HEALTH_* 환경 변수에 저장할 수 있습니다.

  • 도구는 액세스 토큰, 새로 고침 토큰 또는 클라이언트 비밀 키를 절대 반환하지 않습니다.

  • GOOGLE_HEALTH_PRIVACY_MODE=structured가 기본값입니다.

  • raw 모드는 명시적이며 디버깅이나 심층 분석을 위해서만 사용해야 합니다.

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

구성 변경 후에는 /reload-mcp 또는 hermes mcp test google_health를 사용하세요. 일반적인 데이터 액세스를 위해 게이트웨이를 다시 시작할 필요는 없습니다.

개발

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

링크

라이선스

MIT - 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