This server lets AI agents securely read user-authorized Google Health API v4 data (Fitbit, Pixel Watch, partners) locally via OAuth, with tokens never leaving your machine.
Authentication & Setup
Generate an OAuth URL (
google_health_get_auth_url), exchange codes for tokens (google_health_exchange_code) stored locally with0600permissions, and revoke access (google_health_revoke_access).
Health Data Access
List data points (
google_health_list_data_points) — query steps, sleep, heart rate, weight, exercise, etc.Reconcile data streams (
google_health_reconcile_data_points) — merge streams across all-sources, google-wearables, or google-sources.Daily rollup (
google_health_daily_rollup) — aggregate data over civil days.Physical-time rollup (
google_health_rollup) — aggregate over arbitrary time intervals.
User Profile & Identity
Retrieve identity (
google_health_get_identity), profile (google_health_get_profile), and settings like units/timezone (google_health_get_settings).
Summaries & Reports
Daily summary (
google_health_daily_summary) and weekly summary (google_health_weekly_summary) for aggregated health metrics.Wellness context (
google_health_wellness_context) — normalize health data into a standardized shape for recommendation engines, including soreness/injury flags.
Discovery & Diagnostics
Connection status (
google_health_connection_status) — check config, token file, privacy mode, and scope readiness.Data inventory (
google_health_data_inventory) and capabilities (google_health_capabilities) — explore supported types, scopes, and recommended workflows.Agent manifest (
google_health_agent_manifest) — machine-readable install/runtime guide for AI agents.Cache status (
google_health_cache_status) — inspect optional local SQLite cache.Privacy audit (
google_health_privacy_audit) — review privacy posture without exposing secrets.
Privacy & Security
Three privacy modes:
summary,structured(default), andraw.Tokens stored at
~/.google-health-mcp/tokens.json; access tokens, refresh tokens, and client secrets are never returned to the agent.GPS redaction enabled by default.
Allows access to health data from Android devices like Pixel Watch via the Google Health API, including activity, sleep, and health metrics.
Enables reading user-authorized health data from Fitbit devices through the Google Health API, such as steps, sleep, heart rate, and exercise.
Provides tools to read authorized health data from the Google Health API v4, including data from Fitbit, Pixel Watch, and other supported sources.
Click on "Install 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 MCPshow my daily summary for yesterday"
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.
⚡ One-command install with Delx Wellness for Hermes:
npx -y delx-wellness-hermes setup— preconfigures this connector and the other 8 in a dedicated Hermes profile.Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.
Unofficial, local-first MCP server for the new Google Health API v4.
It lets Claude, Cursor, Hermes, OpenClaw and other MCP clients read user-authorized Google Health data from Fitbit, Pixel Watch and supported third-party sources through Google's OAuth 2.0 flow.
Beta status: Google recommends waiting until the end of May 2026 before officially launching Google Health API integrations because breaking changes may occur while developer feedback is incorporated. This connector is intentionally published as an early beta for builders who want to test the API now.
Unofficial project. Not affiliated with, endorsed by or supported by Google, Fitbit or Alphabet. Not a medical device. Not medical advice.
Beta Testers Wanted
The highest-leverage contribution right now is real setup feedback from Fitbit, Pixel Watch, Android and Google Health API v4 users.
If you can test with a real account:
Run
npx -y google-health-mcp-unofficial doctorand confirm the OAuth flow is clear.Try
google_health_connection_status,google_health_data_inventoryandgoogle_health_daily_summaryfrom your MCP client.Open an issue for missing data types, confusing setup steps, client-specific friction or privacy concerns.
Do not paste OAuth tokens, client secrets or personal health measurements into public issues.
Useful links:
Related MCP server: Withings MCP
Why this exists
Google Health API is the successor to Fitbit Web API: new OAuth, new base URL, v4 endpoint schema, standardized data types, reconciled streams and rollups.
This MCP gives agents a clean way to discover the API, check setup, authenticate locally and query data without pasting tokens into prompts or agent configs.
30-second Demo
npx -y google-health-mcp-unofficial setup --scope-preset full
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctorThen start your agent with:
google_health_connection_statusgoogle_health_data_inventorygoogle_health_privacy_auditgoogle_health_daily_summary
Install
Create a Google Cloud OAuth client, enable the Google Health API, and add:
http://127.0.0.1:3000/callbackThen run:
npx -y google-health-mcp-unofficial setup --scope-preset full
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctorScope presets keep OAuth consent easier to reason about:
npx -y google-health-mcp-unofficial setup --scope-preset basic
npx -y google-health-mcp-unofficial setup --scope-preset activity
npx -y google-health-mcp-unofficial setup --scope-preset sleep
npx -y google-health-mcp-unofficial setup --scope-preset fullbasic- profile and settings onlyactivity- profile, settings, activity and health metricssleep- profile, settings and sleepfull- all recommended read-only scopes, including nutrition
If setup gets stuck:
npx -y google-health-mcp-unofficial doctor --fix
npx -y google-health-mcp-unofficial doctor --live
npx -y google-health-mcp-unofficial support --redacteddoctor --fixrepairs local config/token permissions where the OS supportschmod 600.doctor --livecalls safe Google Health identity/profile/settings endpoints after auth to prove the API is reachable.support --redactedprints a copy-paste support bundle for GitHub issues without tokens, secrets or health measurements.
Recommended read-only scopes:
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.readonlyStandalone MCP config:
{
"mcpServers": {
"google_health": {
"command": "npx",
"args": ["-y", "google-health-mcp-unofficial"]
}
}
}Tools
Start here:
google_health_connection_status- local config, token, scope and client readinessgoogle_health_data_inventory- supported domains, scopes, data type naming and agent flowgoogle_health_agent_manifest- machine-readable install/runtime guidegoogle_health_daily_summary- daily beta summary from rollups and reconciled streamsgoogle_health_weekly_summary- weekly beta review
Google Health API methods:
google_health_get_identitygoogle_health_get_profilegoogle_health_get_settingsgoogle_health_list_data_pointsgoogle_health_reconcile_data_pointsgoogle_health_daily_rollupgoogle_health_rollup
Diagnostics:
google_health_get_auth_urlgoogle_health_exchange_codegoogle_health_privacy_auditgoogle_health_cache_statusgoogle_health_revoke_accessgoogle_health_wellness_context
Data Type Notes
Endpoint paths use kebab case:
steps
sleep
heart-rate
daily-resting-heart-rate
daily-heart-rate-variability
active-zone-minutes
total-calories
weight
exerciseFilter expressions use 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"Source families supported by the API:
users/me/dataSourceFamilies/all-sources
users/me/dataSourceFamilies/google-wearables
users/me/dataSourceFamilies/google-sourcesPrivacy
OAuth tokens are stored locally at
~/.google-health-mcp/tokens.jsonwith0600permissions.Secrets can live in
~/.google-health-mcp/config.jsonorGOOGLE_HEALTH_*environment variables.Tools never return access tokens, refresh tokens or client secrets.
GOOGLE_HEALTH_PRIVACY_MODE=structuredis the default.rawmode is explicit and should be used only for debugging or deep analysis.
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 --fix
npx -y google-health-mcp-unofficial doctor --client hermes --live
hermes mcp test google_healthAfter config changes, use /reload-mcp or hermes mcp test google_health. Do not restart the gateway for normal data access.
Development
git clone https://github.com/davidmosiah/google-health-mcp.git
cd google-health-mcp
npm install
npm testLinks
Google Health API: https://developers.google.com/health
REST reference: https://developers.google.com/health/reference/rest
Data types: https://developers.google.com/health/data-types
Migration guide: https://developers.google.com/health/migration
Delx Wellness registry: https://github.com/davidmosiah/delx-wellness
📧 Contact & Support
📨 support@delx.ai — general questions, integration help, partnerships
🐛 Bug reports / feature requests — GitHub Issues
🐦 Updates — @delx369 on X
🌐 Site — wellness.delx.ai
License
MIT - see LICENSE.
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/google-health-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
