Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
MCP server for the Google Health API, with a local SQLite cache and trend analysis.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 15/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/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 | 27/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 MCP. Follow https://mcp.popnx.com/i/partymola-google-health-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 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) 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 MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "google-health": { "command": "uvx", "args": [ "google-health-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) No key is needed. 5) Do what we agreed, then check that the Google Health 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
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"google-health": {
"command": "uvx",
"args": [
"google-health-mcp"
]
}
}
}Use Google Health MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Google Health MCP or shows a Google Health MCP tool in the answer, you are connected
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 MCP yet
Google Health 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 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
Install Python (uv) 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 MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user google-health -- uvx google-health-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) No key is needed. 5) Do what we agreed, then check that the Google Health 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
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user google-health -- uvx google-health-mcpYou should see Google Health MCP listed as connected
Use Google Health MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Google Health MCP or shows a Google Health MCP tool in the answer, you are connected
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
Install Python (uv) 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 MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "google-health": { "command": "uvx", "args": [ "google-health-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) No key is needed. 5) Do what we agreed, then check that the Google Health 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
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Google Health MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Google Health MCP or shows a Google Health MCP tool in the answer, you are connected
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
Install Python (uv) 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 MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "google-health": { "type": "stdio", "command": "uvx", "args": [ "google-health-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) No key is needed. 5) Do what we agreed, then check that the Google Health 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
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Google Health MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Google Health MCP or shows a Google Health MCP tool in the answer, you are connected
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 -- uvx google-health-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"google-health": {
"command": "uvx",
"args": [
"google-health-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"google-health": {
"command": "uvx",
"args": [
"google-health-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"google-health": {
"type": "stdio",
"command": "uvx",
"args": [
"google-health-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based 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 20, 2026
The registry name was verified with the GitHub account partymola, which owns the repo
Code last changed 4 days ago
Uses GPL-3.0
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-mcp@1.12.0
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/partymola-google-health-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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 days ago, and the latest version (1.12.0) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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 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 | No | 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 | GPL-3.0 | 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.
MCP server for the Google Health API, with a local SQLite cache and trend analysis.
Designed for Claude Code and other MCP clients. Your data syncs to a database on your own machine, so queries are fast, work offline, and cost no API quota.
| Tool | Data |
|---|---|
health_get_heart_rate | Resting heart rate |
health_get_activity | Steps, calories, distance, floors |
health_get_exercises | Workouts: name, duration, heart rate, calories, Google's metrics summary, and splits on request |
health_get_exercise_route | One workout's GPS route, as the TCX file Google exports |
health_get_sleep | Duration, stages, sleep period |
health_get_sleep_sessions | Each session as Google recorded it: metadata, summary, and every stage segment on request |
health_get_weight | Weight, body fat %, one row a day |
health_get_weight_readings | Every weigh-in and body-fat reading, as Google recorded each one |
health_get_height | Height readings |
health_get_spo2 | Nightly blood oxygen saturation |
health_get_hrv | Heart rate variability (RMSSD) |
health_get_azm | Active zone minutes, with the per-zone breakdown |
health_get_breathing_rate | Nightly breaths per minute |
health_get_skin_temperature | Nightly variation from your baseline, and the absolutes behind it |
health_get_core_temperature | Body temperature readings you logged by hand |
health_get_cardio_fitness | VO2 max, where the device reports it |
health_get_food_log | Food calories and water, where logged |
health_get_ecg | Electrocardiograms: classification, average rate, duration, waveform on request |
health_get_irregular_rhythm | Irregular-rhythm notifications and the windows that triggered them |
health_get_devices | Paired devices, battery level, last sync |
health_get_profile | Your profile, settings and irregular-rhythm enrolment, as Google returns them |
health_get_lifetime_stats | Totals and best days over the cached history, with its coverage |
health_trends | Aggregated averages and period comparisons |
pip install google-health-mcp
Or run it without installing, in which case every google-health-mcp ... command you run below becomes uvx google-health-mcp ...:
uvx google-health-mcp --version
Every user registers their own OAuth client. This is seven console steps, and the page names are Google's as of August 2026.
Google's own [setup page](https://developers.google.com/health/setup) will send you somewhere else - follow the steps below instead. Its quick-start builds a *Web* client with https://www.google.com as the redirect URI, which suits the OAuth Playground rather than a program running on your machine; this server refuses that file and says so. Use that page only to check whether one of the pages below has been renamed.
403: access_denied.Step 7 is the one that bites, and it is worth checking rather than assuming. While an app's publishing status is Testing, Google issues refresh tokens that expire seven days after consent - so everything works, and then syncing stops a week later with nothing pointing back to this moment. The Audience page can read "In production" while the token server disagrees. Two readings that do not: the verification-status line on the Branding page, and google-health-mcp doctor, which fails loudly when the stored token records a short expiry.
Put the downloaded client JSON where the server looks for it, unedited:
mkdir -p ~/.config/google-health-mcp
cp ~/Downloads/client_secret_*.json ~/.config/google-health-mcp/google_client.json google-health-mcp auth
Your browser will warn that Google hasn't verified this app. That is expected, and the app is your own: these health scopes are classified restricted, and verification only matters above 100 users. Click Advanced, then Go to google-health-mcp (unsafe), and grant the scopes.
If you have more than one Google account, pick the one your health data is in. auth checks the account once the tokens are saved, and if Google reports it is not linked to Google Health, it says so and exits 1; run it again and choose the other account.
The flow listens on localhost:8081 for the callback, so that port must be free. It saves tokens to ~/.config/google-health-mcp/google_tokens.json, created 0600 on POSIX. Windows keeps only the owner-write bit, as its read-only attribute, and governs access by ACLs - so there the file is not restricted to your account, and what it grants is whatever its directory's ACLs pass down. Access tokens last an hour and refresh automatically. Refresh tokens do not rotate, so a token minted on a machine with a browser can be copied to a headless one.
If you authorised before publishing the app, re-run google-health-mcp auth afterwards: publishing does not extend a token already granted, and that one still expires after seven days.
claude mcp add -s user google-health -- google-health-mcp
Running it with uvx instead: claude mcp add -s user google-health -- uvx google-health-mcp.
google-health-mcp doctor
Worth running before step 3 (Authorise) as well as after: it reports whether port 8081 can be bound and whether this host can open a browser, which are the two ways auth fails before it starts.
Offline and read-only: it reports which paths resolved where, whether the credential files are the right shape, whether the token is short-lived, whether the grant holds every permission this version reads, and whether the cache is being kept up to date.
doctor --json reports the same findings for a monitor to act on:
{
"version": "1.12.0", "findings": [ { "check": "stopped-series", "name": "hrv series", "severity": "warn", "detail": "No hrv since 2026-03-30, after rows on 28 of the 30 days before that.", "fix": "Re-sync that type alone (...)" } ], "counts": {"ok": 7, "warn": 1, "fail": 0} }
The payload goes to stdout; logging goes to stderr, so a subprocess consumer should read the two separately.
Match on check, never on name or detail: the first is a stable identifier, the other two are prose and carry the data type. check is null for findings nothing consumes programmatically yet.
The exit code is 1 only when something is graded `fail`, in both formats - a warning never changes it, which is the reason this flag exists: a stopped data series is a warning, so the exit code alone cannot tell you about the one failure most worth watching for.
Check `version` before trusting an absent finding. A build older than a check does not report it, so "no series-never-filled finding" and "this build cannot report one" look identical without it. A release before 1.1.0 rejects --json and exits 2. version is itself null when the package is run from a source tree with no installed distribution metadata - the payload is still emitted, since a diagnostic that dies on a half-configured install is worthless exactly when it is needed.
The payload names the resolved config, database and credential paths, the same way the text report does. That is deliberate - it is what makes a wrong-path setup diagnosable - but a consumer that forwards the payload off the machine is disclosing them. No credential *values* appear in either format.
Query tools sync on first use each day, so you can skip this. To pre-populate the cache, or to pull history older than it:
google-health-mcp sync --days 30
google-health-mcp sync --since 2023-10-01 # backfill
google-health-mcp Start the MCP server (stdio transport)
google-health-mcp -V, --version Print the installed package version google-health-mcp auth Interactive OAuth setup google-health-mcp doctor Check the setup and report what needs fixing --json Emit the findings as JSON, for a monitor rather than a person. Each finding carries a stable check name to match on; the exit code is the same either way. google-health-mcp sync Sync data to the local cache --days N Days of history for a first sync (default: 30) --types TYPE,... Data types to sync (default: all). One or more of: heart_rate, activity, exercises, sleep, weight, spo2, hrv, azm, breathing_rate, skin_temperature, core_temperature, cardio_fitness, food_log, ecg, irn, account, height, exercise_routes, sleep_sessions, weight_readings, body_fat_readings --since YYYY-MM-DD Fetch from this date, ignoring the incremental cursor --until YYYY-MM-DD Inclusive end date for a --since window; together they re-fetch exactly that window, to repair a gap in the middle of the cache google-health-mcp import Import exported JSON data files --data-dir PATH Directory containing the J