Google Health Mcp
by davidmosiahcommunityv0.5.2
32
5
An unofficial local-first MCP server for Google Health API v4 that lets MCP clients authenticate via OAuth and read user-authorized health data from Fitbit, Pixel Watch, and supported partner sources. It also provides setup and diagnostic commands for checking local configuration, OAuth, access, and data availability.
From the registry: Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Install & configure
Prerequisites
- required
- requiredCreate a Google Cloud OAuth clientCreate OAuth 2.0 credentials for Google Health API access.https://developers.google.com/health
- requiredEnable the Google Health APIEnable the Google Health API in your Google Cloud project before authenticating.https://developers.google.com/health
- requiredAdd the OAuth redirect URIConfigure your OAuth client to allow the local callback URI: http://127.0.0.1:3000/callback
- requiredRun local setup and authenticationInitialize local config, choose scopes, and complete the OAuth flow before using the MCP server.
$ npx -y google-health-mcp-unofficial setup --scope-preset full npx -y google-health-mcp-unofficial auth npx -y google-health-mcp-unofficial doctor
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `google-health-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js and npm** — Required to run the MCP server via npx. (https://nodejs.org/)
- **Create a Google Cloud OAuth client** — Create OAuth 2.0 credentials for Google Health API access. (https://developers.google.com/health)
- **Enable the Google Health API** — Enable the Google Health API in your Google Cloud project before authenticating. (https://developers.google.com/health)
- **Add the OAuth redirect URI** — Configure your OAuth client to allow the local callback URI: http://127.0.0.1:3000/callback
- **Run local setup and authentication** — Initialize local config, choose scopes, and complete the OAuth flow before using the MCP server. Run: `npx -y google-health-mcp-unofficial setup --scope-preset full
npx -y google-health-mcp-unofficial auth
npx -y google-health-mcp-unofficial doctor`
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","google-health-mcp-unofficial"]
- optional environment variables:
- `GOOGLE_HEALTH_CLIENT_ID`: Google OAuth client ID. The README says secrets can live in ~/.google-health-mcp/config.json or GOOGLE_HEALTH_* environment variables. (example: `<your-google-oauth-client-id>`)
- `GOOGLE_HEALTH_CLIENT_SECRET`: Google OAuth client secret. The README says secrets can live in ~/.google-health-mcp/config.json or GOOGLE_HEALTH_* environment variables. (example: `<your-google-oauth-client-secret>`)
- `GOOGLE_HEALTH_PRIVACY_MODE`: Privacy output mode. Default is structured; raw is explicit and intended only for debugging or deep analysis. (example: `<structured-or-raw>`)
Note: The simplest install path is via npx. The README's standalone MCP config only specifies command and args. OAuth tokens are stored locally in ~/.google-health-mcp/tokens.json, and client secrets may be stored either in ~/.google-health-mcp/config.json or provided through GOOGLE_HEALTH_* environment variables. Scope selection is handled during the one-time setup command, not in the MCP config.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: The simplest install path is via npx. The README's standalone MCP config only specifies command and args. OAuth tokens are stored locally in ~/.google-health-mcp/tokens.json, and client secrets may be stored either in ~/.google-health-mcp/config.json or provided through GOOGLE_HEALTH_* environment variables. Scope selection is handled during the one-time setup command, not in the MCP config.
Tools (18)
google_health_connection_status
Checks local config, token, scope, and client readiness.
google_health_data_inventory
Lists supported domains, scopes, data type naming, and agent flow.
google_health_agent_manifest
Returns a machine-readable install/runtime guide.
google_health_daily_summary
Produces a beta daily summary from rollups and reconciled streams.
google_health_weekly_summary
Produces a beta weekly review summary.
google_health_get_identity
Fetches Google Health identity information.
google_health_get_profile
Fetches profile data.
google_health_get_settings
Fetches settings data.
google_health_list_data_points
Lists available health data points.
google_health_reconcile_data_points
Reconciles data points from multiple sources.
google_health_daily_rollup
Returns daily aggregated rollup data.
google_health_rollup
Returns rollup data.
google_health_get_auth_url
Generates the OAuth authorization URL.
Environment variables
GOOGLE_HEALTH_*Environment variables used to supply Google Health secrets and configuration.GOOGLE_HEALTH_PRIVACY_MODEControls output format for privacy-related handling; default is structured.Packages
google-health-mcp-unofficial
npmv0.5.2transport: stdio
Details
- Language
- TypeScript
- License
- MIT
- Released
- Jul 13, 2026
- Last commit
- Jul 22, 2026
- Registry name
- io.github.davidmosiah/google-health-mcp