Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
If you already use Google, the google mcp server is the piece that lets your assistant work with it directly. Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
google_health_connection_status — local config, token, scope and client readinessgoogle_health_data_inventory — supported domains, scopes, data type naming and agent flowgoogle_health_data_type_coverage — static coverage plan, or explicit live read-only validation for issue #21google_health_daily_summary — daily beta summary from rollups and reconciled streamsgoogle_health_weekly_summary — weekly beta reviewgoogle_health_privacy_audit — what is stored locally and what is sent to GoogleInstallation goes through your MCP client rather than a global install: point it at delx-wellness-hermes on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google's toolset — google_health_connection_status, google_health_data_inventory, google_health_data_type_coverage and 3 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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 |
Standalone MCP config:
```json
{
"mcpServers": {
"google_health": {
"command": "npx",
"args": ["-y", "google-health-mcp-unofficial"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.