Google Health Fitbit MCP server

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_data_point

  Fetch one data point by id — e.g. a specific sleep session, exercise or weight entry found via list/reconcile. Accepts the bare id or the full resource name from a previous response. Only data types whose official_operations include 'get' support this (see google_health_list_data_types).

• google_health_get_identity

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

• google_health_get_irn_profile

  Get the user's irregular rhythm notification (IRN) engagement status — whether the AFib detection feature is enabled on their Fitbit/Pixel Watch. Requires the googlehealth.irn.readonly scope (setup --scope-preset heart). Read-only, non-diagnostic.

• 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_list_paired_devices

  List the Fitbit trackers, Pixel Watches and other devices paired to the authenticated Google Health account. Useful to answer 'is my watch syncing?' and to see which device produces which data. Read-only.

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

• 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 53 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

78/100

higher than 57% of 48,255 servers

Tools

29

the typical server has 7

Tools that change things

3%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

16

more than 90% of 28,688 servers

Downloads a week

99

more than 63% of 12,191 servers with a package

Google Health Fitbit: common questions

Is Google Health Fitbit MCP server safe?

Mostly: it is graded B (78/100). Read the Google Health Fitbit safety report

How do I install Google Health Fitbit?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Google Health Fitbit need an API key?

Yes. The registry entry asks for GOOGLE_HEALTH_CLIENT_SECRET.

Is Google Health Fitbit maintained?

The last commit was 92 days ago (2026-08-04). The latest release is v1.0.2.

How does Google Health Fitbit compare with other MCP servers?

safety score 78/100 (higher than 57% of 48,255 servers); tools 29 (the typical server has 7); tools that change things 3% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.