Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
Privacy-first Google Health API MCP server for health, sleep, activity and HR agents
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 16/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 19/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Google Health Fitbit MCP. Follow https://mcp.popnx.com/i/berkkilicoglu-google-health-fitbit-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Google Health Fitbit MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Google Health Fitbit MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "google-health-fitbit": { "command": "npx", "args": [ "-y", "google-health-fitbit-mcp" ], "env": { "GOOGLE_HEALTH_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For GOOGLE_HEALTH_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Google Health Fitbit MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
SettingsDeveloperEdit Config
{
"mcpServers": {
"google-health-fitbit": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
],
"env": {
"GOOGLE_HEALTH_CLIENT_SECRET": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Google Health Fitbit MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Google Health Fitbit MCP or shows a Google Health Fitbit MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
GOOGLE_HEALTH_CLIENT_ID Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_REDIRECT_URI Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_TOKEN_PATH Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.GOOGLE_HEALTH_PRIVACY_MODE Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.GOOGLE_HEALTH_CACHE Optional SQLite cache toggle. Set to true or sqlite to enable.GOOGLE_HEALTH_CACHE_PATH Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.GOOGLE_HEALTH_NO_CACHE Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Google Health Fitbit MCP yet
Google Health Fitbit MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Google Health Fitbit MCP
B · Others in Clinics & health that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Google Health Fitbit MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Google Health Fitbit MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user google-health-fitbit --env GOOGLE_HEALTH_CLIENT_SECRET=your-value -- npx -y google-health-fitbit-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For GOOGLE_HEALTH_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Google Health Fitbit MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user google-health-fitbit --env GOOGLE_HEALTH_CLIENT_SECRET=your-value -- npx -y google-health-fitbit-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Google Health Fitbit MCP listed as connected
Use Google Health Fitbit MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Google Health Fitbit MCP or shows a Google Health Fitbit MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
GOOGLE_HEALTH_CLIENT_ID Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_REDIRECT_URI Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_TOKEN_PATH Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.GOOGLE_HEALTH_PRIVACY_MODE Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.GOOGLE_HEALTH_CACHE Optional SQLite cache toggle. Set to true or sqlite to enable.GOOGLE_HEALTH_CACHE_PATH Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.GOOGLE_HEALTH_NO_CACHE Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Google Health Fitbit MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Google Health Fitbit MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "google-health-fitbit": { "command": "npx", "args": [ "-y", "google-health-fitbit-mcp" ], "env": { "GOOGLE_HEALTH_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For GOOGLE_HEALTH_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Google Health Fitbit MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Google Health Fitbit MCP settings, GOOGLE_HEALTH_CLIENT_SECRET is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Google Health Fitbit MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Google Health Fitbit MCP or shows a Google Health Fitbit MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
GOOGLE_HEALTH_CLIENT_ID Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_REDIRECT_URI Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_TOKEN_PATH Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.GOOGLE_HEALTH_PRIVACY_MODE Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.GOOGLE_HEALTH_CACHE Optional SQLite cache toggle. Set to true or sqlite to enable.GOOGLE_HEALTH_CACHE_PATH Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.GOOGLE_HEALTH_NO_CACHE Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Google Health Fitbit MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Google Health Fitbit MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "google-health-fitbit": { "type": "stdio", "command": "npx", "args": [ "-y", "google-health-fitbit-mcp" ], "env": { "GOOGLE_HEALTH_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For GOOGLE_HEALTH_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Google Health Fitbit MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Google Health Fitbit MCP settings, GOOGLE_HEALTH_CLIENT_SECRET is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Google Health Fitbit MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Google Health Fitbit MCP or shows a Google Health Fitbit MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
GOOGLE_HEALTH_CLIENT_ID Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_REDIRECT_URI Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.GOOGLE_HEALTH_TOKEN_PATH Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.GOOGLE_HEALTH_PRIVACY_MODE Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.GOOGLE_HEALTH_CACHE Optional SQLite cache toggle. Set to true or sqlite to enable.GOOGLE_HEALTH_CACHE_PATH Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.GOOGLE_HEALTH_NO_CACHE Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user google-health-fitbit --env GOOGLE_HEALTH_CLIENT_SECRET=your-value -- npx -y google-health-fitbit-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"google-health-fitbit": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
],
"env": {
"GOOGLE_HEALTH_CLIENT_SECRET": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"google-health-fitbit": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
],
"env": {
"GOOGLE_HEALTH_CLIENT_SECRET": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"google-health-fitbit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
],
"env": {
"GOOGLE_HEALTH_CLIENT_SECRET": "your-value"
}
}
}
}GOOGLE_HEALTH_CLIENT_ID envGOOGLE_HEALTH_CLIENT_SECRET secret required envGOOGLE_HEALTH_REDIRECT_URI envGOOGLE_HEALTH_TOKEN_PATH envGOOGLE_HEALTH_PRIVACY_MODE envGOOGLE_HEALTH_CACHE envGOOGLE_HEALTH_CACHE_PATH envGOOGLE_HEALTH_NO_CACHE envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: google-health-fitbit-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account BerkKilicoglu, which owns the repo
Code last changed 4 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for google-health-fitbit-mcp@1.0.2
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/berkkilicoglu-google-health-fitbit-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GOOGLE_HEALTH_CLIENT_SECRET
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 4 months ago, and the latest version (1.0.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
An MCP server that provides CodeScene Code Health analysis tools.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
| This one Google Health Fitbit MCP | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| License | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Google Health Fitbit MCP
Query your own Google Health API data — Fitbit, Pixel Watch and connected partner sources — over local OAuth. Beta .
Everything runs on your own machine — your credentials never leave your device .
An MCP server that runs locally and hands your AI agent your own Google Health API data — from Fitbit trackers, Pixel Watch and supported partner sources — through OAuth.
npx -y google-health-fitbit-mcp setup0600 permissions and are never returned by any tool (privacy).Beta status: Google Health API is available to developers but the surface is still moving. Because Google's release notes keep listing scope and data-type changes after launch, this connector remains in beta and steers testers toward safe read-only validation before any production use.
Independent, community-built connector — no affiliation with, endorsement from or support by Google, Fitbit or Alphabet. Not a medical device or medical advice; treat the data as trend context only.
Prerequisite: a Google Cloud OAuth client (type: Desktop) with the Google Health API enabled and the redirect
http://127.0.0.1:3000/callbackregistered — details in Install.
Step 1 — Install & authorize (once):
npx -y google-health-fitbit-mcp setup # guided: Google Cloud OAuth client + scopes
npx -y google-health-fitbit-mcp auth # browser OAuth — tokens stay on your machine npx -y google-health-fitbit-mcp checkup # ✓ verifies everything is ready
🔑 First time? Get your Google Client ID & Secret (~2 min)
setup asks for a Client ID and Client Secret. You create these once, for free, in Google Cloud:
health-mcp), click Create, then select it.403: access_denied.…apps.googleusercontent.com) and the Client secret, then paste each one when setup prompts you.Redirect URI: Desktop-app clients allow the
http://127.0.0.1:3000/callbackloopback automatically — you don't register it anywhere. Just press Enter to accept the default whensetupasks. For every othersetupprompt (scope preset, privacy mode), pressing Enter picks a sensible default.
Heads-up — the 7-day rule: while the consent screen sits in Testing publishing status, Google revokes refresh tokens after 7 days. Around once a week the next request fails with
invalid_grant, which is normal and not a bug in this server. It reopens the consent flow for you (see Staying connected); approving takes a couple of seconds. Publishing the app removes the expiry entirely — check what your scopes require on the consent screen before switching.
Step 2 — Connect your app:
Claude Code
claude mcp add google-health -- npx -y google-health-fitbit-mcp
Claude Desktop
Settings → Developer → Edit Config, then add to claude_desktop_config.json:
{
"mcpServers": { "google_health": { "command": "npx", "args": ["-y", "google-health-fitbit-mcp"] } } }
Restart Claude Desktop — the tools appear under the 🔌 connectors menu.
Cursor
Add the same mcpServers block to .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global), or use Settings → MCP → Add new server.
{
"mcpServers": { "google_health": { "command": "npx", "args": ["-y", "google-health-fitbit-mcp"] } } }
Windsurf
Add the same mcpServers block to ~/.codeium/windsurf/mcp_config.json.
Hermes
npx -y google-health-fitbit-mcp setup --client hermes # writes the Hermes config for you
Then reload with /reload-mcp or hermes mcp test google_health.
Step 3 — Test it. Ask your agent:
Run google_health_connection_status and tell me if I'm connected.
The Google Health API is the successor to the Fitbit Web API: new OAuth, new base URL (https://health.googleapis.com), a streamlined endpoint schema, standardized kebab-case data types, reconciled cross-source streams and daily/physical-time rollups.
It gives agents a clean path to explore the API, verify their setup, sign in locally and pull data — with no need to paste tokens into prompts or agent configs.
Three good opening prompts, built around tools this connector genuinely ships:
Check my setup with google_health_connection_status, then call
google_health_data_inventory and tell me which Google Health domains and scopes I've granted.
Pull today's google_health_daily_summary, then google_health_weekly_summary.
Keep observed data separate from any suggestions, and stay non-medical.
List my paired devices with google_health_list_paired_devices and tell me
which device is producing my sleep and heart-rate data.
29 tools, all read-only except the two explicitly gated local-profile/auth actions noted below.
| Tool | What it does |
|---|---|
google_health_connection_status | Local config, token, scope and MCP-client readiness — no Google call |
google_health_quickstart | Personalized 3-step setup walkthrough that adapts to your current state |
google_health_data_inventory | Supported domains, scopes, data-type naming and recommended agent flow |
google_health_list_data_types | The 39 kebab-case data-type slugs with units, scopes and supported verbs |
google_health_demo | Realistic synthetic payloads so agents see the contract before real calls |
| Tool | Endpoint |
|---|---|
google_health_get_identity | /v4/users/me/identity — Google Health + legacy Fitbit identity mapping |
google_health_get_profile | /v4/users/me/profile |
google_health_get_settings | /v4/users/me/settings — units, timezone |
google_health_list_paired_devices | /v4/users/me/pairedDevices — your Fitbit trackers and Pixel Watches, and which device produces which data |
google_health_get_irn_profile | /v4/users/me/irnProfile — irregular-rhythm (AFib) notification engagement status |
google_health_list_data_points | /v4/.../dataPoints — intraday detail for any data type |
google_health_get_data_point | /v4/.../dataPoints/{id} — one specific sleep session, exercise or measurement |
google_health_reconcile_data_points | /v4/.../dataPoints:reconcile — one clean stream across sources (all-sources, google-wearables, google-sources) |
google_health_daily_rollup | /v4/.../dataPoints:dailyRollUp — civil-day aggregates |
google_health_rollup | /v4/.../dataPoints:rollUp — physical-time window aggregates |
| Tool | What it does |
|---|---|
google_health_daily_summary | Steps, distance, calories, active-zone minutes, sleep, resting HR, HRV and weight for one day, with data-quality flags |
google_health_weekly_summary | Weekly scorecard with optional prior-window comparison, load classification and bottlenecks |
google_health_wellness_context | Normalized activity/sleep context for recommendation engines |
google_health_get_auth_url · google_health_exchange_code (gated: requires explicit user intent) · google_health_revoke_access (gated + destructive: disconnects Google Health) · google_health_privacy_audit · google_health_cache_status · google_health_data_type_coverage · google_health_capabilities · google_health_agent_manifest · google_health_onboarding · google_health_profile_get · google_health_profile_update (local file only, requires explicit_user_intent=true)
MCP resources: google-health://agent-manifest, google-health://capabilities, google-health://inventory, google-health://latest/steps, google-health://profile, google-health://summary/daily, google-health://summary/weekly.
MCP prompts: google_health_daily_checkin, google_health_weekly_review, google_health_data_type_investigation.
39 data types from the official Google Health table, including steps, sleep, heart-rate, heart-rate-variability, daily-resting-heart-rate, active-zone-minutes, distance, total-calories, weight, body-fat, blood-glucose, oxygen-saturation, vo2-max, electrocardiogram, irregular-rhythm-notification, exercise, floors, swim-lengths-data, nutrition-log and hydration-log.
Naming rules agents need:
steps, daily-resting-heart-rate.sleep.interval.civil_start_time, heart_rate.sample_time.physical_time.all-sources, google-wearables, google-sources.Call google_health_list_data_types for the full catalog with units, scopes and which verbs (list/reconcile/rollup) each type supports.
~/.google-health-mcp/tokens.json, locked d