Log inSubmit server
Google Health MCP logo

Google Health MCP

Reads user-authorized Google Health API v4 data locally for health, sleep, activity, and heart-rate agent workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Health MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-health-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-health-mcp-unofficial"
      ],
      "env": {
        "GOOGLE_HEALTH_MCP_HOST": "YOUR_VALUE_HERE",
        "GOOGLE_HEALTH_MCP_PORT": "YOUR_VALUE_HERE",
        "GOOGLE_HEALTH_MCP_TRANSPORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y google-health-mcp-unofficial

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 13d ago.

Overview

The google-health-mcp MCP server exposes user-authorized Google Health API v4 data to agents through local OAuth. It supports Fitbit, Pixel Watch, and partner data, with tools for connection checks, coverage discovery, daily and weekly summaries, and privacy auditing. Use it when an agent needs read-only wellness data without placing OAuth tokens in prompts or agent configuration. The project is beta, unofficial, and available over stdio by default or optional loopback Streamable HTTP.

Use cases

  • Check Google Health OAuth readiness and authorized scopes
  • Query daily and weekly wellness summaries
  • Inspect supported health data types and domains
  • Audit local token storage and outbound data
  • Validate read-only API coverage

Key features

  • Local OAuth for Google Health API v4
  • Fitbit, Pixel Watch, and partner data access
  • Daily and weekly health summaries
  • Connection, inventory, and coverage diagnostics
  • Privacy audit reporting
  • Stdio and optional loopback Streamable HTTP transports

Tools6

What Google Health MCP lets your agent do. Expand a tool for its parameters.

Self-reported~118 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

15/15 checks healthy over the last 53d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · google-health-mcp-unofficial (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars79Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed6Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Health MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Health MCP

google-health-mcp is an MCP server that connects AI agents to user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners. Its main tools check connection readiness, inventory domains and scopes, inspect data-type coverage, produce daily and weekly summaries, and audit local storage and data sent to Google.

Install it with `npx -y google-health-mcp-unofficial setup`. Before authentication, create a Google Cloud OAuth client, enable the Google Health API, and add `http://127.0.0.1:3000/callback`; then run `auth` and `doctor`.

Yes, google-health-mcp can be wired into Cursor.

OAuth tokens remain on the machine running google-health-mcp and are not placed in prompts or agent configuration. The privacy audit tool reports what is stored locally and what would be sent to Google on a later call.

Related MCP servers

All in Biology & Bioinformatics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Health MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-health-mcp?style=directory)](https://allmcps.com/mcp/google-health-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/google-health-mcp"><img src="https://allmcps.com/api/badge/google-health-mcp?style=directory" alt="Google Health MCP on AllMCPs" /></a>