# google-health-mcp [Health: Active]

**Category:** 🧬 Biology & Bioinformatics  
**Repository:** https://github.com/davidmosiah/google-health-mcp  
**GitHub Stars:** 79  
**npm Downloads (last month):** 1658  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-health-mcp

## Description
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

## Tools
Capabilities this server exposes over MCP:

- **google_health_connection_status** — local config, token, scope and client readiness
- **google_health_data_inventory** — supported domains, scopes, data type naming and agent flow
- **google_health_data_type_coverage** — static coverage plan, or explicit live read-only validation for issue #21
- **google_health_daily_summary** — daily beta summary from rollups and reconciled streams
- **google_health_weekly_summary** — weekly beta review
- **google_health_privacy_audit** — what is stored locally and what is sent to Google

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "google-health-mcp": {
    "command": "npx",
    "args": ["-y","google-health-mcp-unofficial"],
    "env": {
      "GOOGLE_HEALTH_MCP_HOST": "",
      "GOOGLE_HEALTH_MCP_PORT": "",
      "GOOGLE_HEALTH_MCP_TRANSPORT": ""
    }
  }
}
```

**Requires environment variables:** `GOOGLE_HEALTH_MCP_HOST`, `GOOGLE_HEALTH_MCP_PORT`, `GOOGLE_HEALTH_MCP_TRANSPORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What google-health-mcp MCP server does

The google-health-mcp MCP server gives an MCP client access to user-authorized Google Health API v4 data through a local process. The API covers data associated with Fitbit, Pixel Watch, and partner sources. Its intended use is agent-assisted review of health, sleep, activity, and heart-rate information rather than medical diagnosis or treatment.

The connector is read-oriented. It helps an agent understand which domains and scopes are available, inspect readiness, review supported data types, and request beta daily or weekly summaries. It also provides a privacy audit describing local storage and information sent to Google during subsequent calls.

## How it works

OAuth runs locally after the user creates a Google Cloud OAuth client, enables the Google Health API, and configures the loopback redirect at `http://127.0.0.1:3000/callback`. Access tokens are saved on the local machine and are not sent through prompts or agent configuration. The MCP process then makes authorized requests to Google Health API v4 when a tool requires live data.

The default transport is stdio. An optional stateless Streamable HTTP mode listens on loopback, with a health endpoint at `/health` and MCP requests at `/mcp`. HTTP settings can be supplied through host, port, and transport environment variables.

## Setup and configuration

Install the unofficial npm package with `npx -y google-health-mcp-unofficial`. The documented setup sequence is:

1. Create a Google Cloud OAuth client, enable Google Health API access, and add the loopback redirect.
2. Run `npx -y google-health-mcp-unofficial setup --scope-preset full` to write local configuration.
3. Run `npx -y google-health-mcp-unofficial auth` to complete OAuth and save tokens locally.
4. Run `npx -y google-health-mcp-unofficial doctor` to check readiness.

For a live connectivity check, `doctor --live` calls safe identity, profile, and settings endpoints after authentication. Headless OAuth is also available through `auth --manual` for SSH, containers, and WSL. The optional HTTP mode uses `GOOGLE_HEALTH_MCP_HOST`, `GOOGLE_HEALTH_MCP_PORT`, and `GOOGLE_HEALTH_MCP_TRANSPORT=http`.

## Tools and capabilities

The google-health-mcp MCP server exposes six documented tools:

- `google_health_connection_status` checks local configuration, token state, scopes, and client readiness.
- `google_health_data_inventory` describes supported domains, scopes, data-type naming, and the suggested agent flow.
- `google_health_data_type_coverage` reports static coverage or performs explicit live, read-only validation for the referenced coverage issue.
- `google_health_daily_summary` returns a beta daily view based on rollups and reconciled streams.
- `google_health_weekly_summary` provides a beta weekly review.
- `google_health_privacy_audit` reports what is stored locally and what would be sent to Google.

## Limitations and notes

Google Health API v4 and this connector are in beta, so scopes and data types may change. Coverage should be treated as an evolving plan; the live coverage command is designed for read-only validation and redacted reports. The project is unofficial and is not affiliated with Google, Fitbit, or Alphabet.

This tool is not a medical device and does not provide medical advice. Summaries should remain non-medical and distinguish observed data from suggestions. The local-first design protects token handling on the machine running the connector, but it does not turn the underlying health data into a clinical record or guarantee that every partner data type is available.

_Full upstream README: https://allmcps.com/mcp/google-health-mcp/readme_