Google Health MCP
Summary: Use this local MCP server to query a connected Google Health/Fitbit account through 17 read-only tools for metrics, summaries, trends, diagnostics, and account metadata.
Discover supported Google Health API v4 data types and explain the server’s data source and read-only boundaries.
Read raw or normalized metrics for date ranges and recent windows, with source filters, deduplication, source priority, and optional daily rollups.
Get current-day health snapshots and daily, activity, sleep, recovery, and body-metric summaries.
Calculate trends and compare recent periods against preceding periods.
Diagnose data quality, coverage, missing records, provenance, and sync/account status.
Read profile, paired devices, and settings.
Remain read-only: no create/update/delete tools, arbitrary HTTP access, or write operations.
Provides read-only access to a user's Google Health account, with tools for source information, metric discovery, profile/devices/settings, metric reads, daily and recent summaries, trends, sleep summaries, sync availability, period comparisons, data quality, activity, recovery, and body metrics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Health MCP How did I sleep last night?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An unofficial, reusable starting point for connecting your own Google Health account to an MCP client or TypeScript application. One repository contains the shared API client, 17 read-only MCP tools, local OAuth setup, analytics, and synthetic tests.
template ZIP · Preview · v0.2.1
Use this template · Setup · Security and privacy · Upstream attribution
Start here
Requires Node.js 22.13 or newer and npm. Use your own Google Cloud project, OAuth client and Google Health account. The template includes no working credentials or personal health records.
npm ci --ignore-scripts
npm run build
cp .env.example .env
# Fill in your own OAuth client ID and secret, following docs/SETUP.md.
npm run authOAuth setup prints a Google authorization URL for your system browser. It uses state, PKCE and a loopback callback, checks Google Health account linkage, then saves tokens outside the repository. MFA/passkeys and consent stay with the person authorizing the account.
Configure your MCP client to run Node directly, using absolute paths:
{
"mcpServers": {
"google-health": {
"command": "node",
"args": [
"--env-file=/absolute/path/to/google-health-mcp/.env",
"/absolute/path/to/google-health-mcp/dist/src/index.js"
]
}
}
}Adapt the surrounding configuration to your MCP host. Discovery works before authorization; account-dependent tools return an actionable connection error until setup is complete. Use get_data_source_info before interpreting results.
Related MCP server: google-health-mcp
Shared client and tools
src/google-health.ts is the single HTTP client used by the server. src/client.ts exports that client for direct application use; src/mcp.ts builds the MCP server around it. src/oauth.ts and src/auth.ts supply local authorization. There is no independently maintained client repository to keep in sync.
The 17 tools cover source information, metric discovery, profile/devices/settings, metric reads, daily/recent summaries, trends, sleep summaries, sync availability, period comparisons, data quality, activity, recovery and body metrics. All tools are read-only. Daily aggregation uses a read-only POST; the server exposes no create/update/delete or arbitrary HTTP tool.
The client bounds request time, response size, retries and pagination; refuses redirects and unsupported endpoints; and reports safe error codes. Missing, unavailable and zero values remain distinct. Provider data can differ by account, device, scope and synchronization state.
Validate without an account
npm testTests use fake responses and temporary files, including actual MCP protocol and stdio sessions, OAuth callback rejection/replay handling, token-file permissions, account linkage, request bounds and analytics. No real provider calls or account authorization are performed by these checks. Passing tests does not establish live Google API access, device parity or medical validity.
This is a local stdio template. Remote ChatGPT integrations need a separately secured HTTPS MCP deployment and authentication flow; those are not supplied as a hosted service. Personal deployments, dashboards, schedules, private configuration and health data remain separate.
License and provenance
MIT. Adapted from rickygarim/fitbit-google-health-mcp, preserving Rithvik Garimella's attribution, with client/error-handling and template improvements by Kian Konrad. Not affiliated with Google or Fitbit. See ATTRIBUTION.md.
Available Tools
17 toolscompare_periodsBRead-onlyIdempotent
Compare a recent period with the immediately preceding period using daily numeric values and percent changes.
Inputs: days, source, timezone, data_types, +2 more.
get_activity_summaryBRead-onlyIdempotent
Summarize recent movement, distance, calories, floors, and heart-rate-zone activity.
Inputs: days, source, timezone, deduplicate, +1 more.
get_body_metricsBRead-onlyIdempotent
Summarize recent weight, body-fat, temperature, height, and blood-glucose records with normalized units and source metadata.
Inputs: days, source, timezone, deduplicate, +1 more.
get_daily_summaryBRead-onlyIdempotent
Read the most useful daily Fitbit metrics in one call: steps, calories, distance, active minutes, active zone minutes, resting heart rate, HRV, oxygen saturation, respiratory rate, sleep, and weight where available.
Inputs: date (required), source, deduplicate, source_priority.
get_data_qualityARead-onlyIdempotent
Diagnose recent Fitbit data coverage, missing records, source provenance, and API-limited metrics without treating missing data as zero.
Inputs: days, source, timezone, data_types, +2 more.
get_data_source_infoARead-onlyIdempotent
Explain exactly where this server gets health data, which API it uses, its read-only boundaries, and known availability limitations. Call this before interpreting metric results.
Inputs: no named parameters.
get_devicesARead-onlyIdempotent
List devices paired with the connected Google Health account, including the Fitbit Air when exposed by the account.
Inputs: no named parameters.
get_health_snapshotBRead-onlyIdempotent
Return a compact current-day Fitbit snapshot including activity, heart rate, body composition, sleep, freshness, and unavailable metrics.
Inputs: date, source, timezone, deduplicate, +1 more.
get_metricsARead-onlyIdempotent
Read one or more Google Health API v4 metric types for a date/time range. Use list_available_metrics for supported names. Returns raw normalized API records and source metadata.
Inputs: end (required), start (required), data_types (required), source, +3 more.
get_profileARead-onlyIdempotent
Read the connected Google Health/Fitbit profile and identity metadata.
Inputs: no named parameters.
get_recent_metricsBRead-onlyIdempotent
Read recent Fitbit metrics with a safe default 7-day range. Each metric is isolated so unsupported or unavailable types do not fail the whole response.
Inputs: days, source, timezone, data_types, +3 more.
get_recovery_summaryBRead-onlyIdempotent
Summarize sleep, heart rate, HRV, oxygen saturation, and respiratory-rate data for informational recovery context.
Inputs: days, source, timezone, deduplicate, +1 more.
get_settingsARead-onlyIdempotent
Read connected Fitbit/Google Health settings and configured preferences.
Inputs: no named parameters.
get_sleep_summaryBRead-onlyIdempotent
Return normalized sleep sessions and stage totals for a recent date range.
Inputs: days, source, timezone, deduplicate, +1 more.
get_sync_statusBRead-onlyIdempotent
Check connected Fitbit/Google Health account metadata, paired devices, and whether core metrics have recent data.
Inputs: source, deduplicate, source_priority.
get_trendsBRead-onlyIdempotent
Calculate numeric trend summaries for recent Fitbit metrics: count, average, minimum, maximum, first value, last value, and percent change where possible.
Inputs: days, source, timezone, data_types, +2 more.
list_available_metricsARead-onlyIdempotent
List Google Health API v4 data types available through this Fitbit-synced Google Health integration. This is not a direct Fitbit Web API catalog.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Several tools are hard to tell apart: get_health_snapshot, get_daily_summary, get_activity_summary, and get_recovery_summary all return overlapping subsets of the same daily Fitbit metrics, and get_metrics vs get_recent_metrics vs get_trends vs compare_periods all read numeric ranges with different wrappers. get_data_source_info, get_data_quality, and get_sync_status also sit close together (provenance vs coverage vs account state) even though descriptions attempt to differentiate them. The list/get primitives (profile, devices, settings, sleep) are clearly distinct.
Every tool follows a snake_case verb_noun pattern (get_*, list_*, compare_*), with no camelCase or stylistic drift. Names map predictably onto the returned resource, making the surface easy to scan.
17 tools is at the heavy end for a read-only metrics server, and much of that count comes from summary variants (snapshot, daily, activity, recovery, body) that largely recombine the same underlying metrics. The count is defensible given the breadth of health domains, but a few tools feel redundant rather than earning their place.
For an explicitly read-only integration, coverage is solid: discovery, raw metric reads, trends, period comparison, data-quality diagnostics, sleep, body, activity, recovery, plus account/device/profile/settings context. Gaps remain in nutrition/water intake, exercise/activity session logs, and intraday heart-rate resolution, which agents may need to work around.
Maintenance
Related MCP Connectors
Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Household health records with source attribution. Read and add records with OAuth approval.
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceRead-only MCP access to Fitbit-synced health data through Google Health API v4. Provides tools for metrics, summaries, trends, and data quality without write or arbitrary HTTP operations.MIT
- FlicenseAqualityCmaintenanceProvides local, read-only MCP access to Google Health API v4, enabling users to query recorded workouts, heart-rate samples, and related health data through natural language in an MCP client.3-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to access Oura Ring health data such as sleep, readiness, activity, workouts, HRV, and event-centered recovery timelines using OAuth2 authentication.MIT
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that gives MCP clients read-only, OAuth-authenticated access to Google Health API data such as activity, sleep, heart, body, nutrition and ECG records. It exposes tools for profiles, paired devices, data points, daily summaries and time-window rollups, and is deployed on Cloudflare Workers.1MIT