A
licenseB
qualityA
maintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.
26
372 npm
57
MIT
healthCare
by harrylabsj
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@healthCareRecord my latest blood pressure and heart rate."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
healthCare
Local-first personal health management with evidence-linked records and scoped MCP tools.
All health data lives in an encrypted Vault (AES-GCM, passphrase-derived key) on the user's own machine. Agents never touch the Vault directly: they connect to an authenticated local IPC daemon over a unix socket with a paired-agent token that lives only in the macOS Keychain. Every mutation is audit-chained; deletions keep a snapshot behind an approval grant.
MCP tools (24): vitals, medications, activities, emotions, sleep, encounters, diagnosis mentions, medication plans, reminders, trend summaries, timelines, visit-summary preparation, source evidence — all scoped per person and per agent.
Zero network by default. An optional, user-configured LLM endpoint (
HEALTHCARE_LLM_API_KEY/HEALTHCARE_LLM_ENDPOINT) exists for assisted report import; it is off unless explicitly configured.Zero-config Hermes mode:
healthcare-hermesbootstraps Vault, daemon and agent pairing automatically underHEALTHCARE_HOME(the Hermes plugin data directory), then serves stdio MCP.macOS only (agent pairing uses the macOS Keychain). Python ≥ 3.11.
Quick start (Hermes plugin)
Install the healthcare Hermes plugin — no manual setup needed. Or standalone:
uvx --from healthCare==0.2.0 healthcare-hermesState layout under HEALTHCARE_HOME (default ~/.local/share/healthcare):
Path | What |
| encrypted Vault (AES-GCM) |
| generated random passphrase, 0600 |
| local IPC socket |
| non-secret pairing profile (agent_id / host_id / person_id) |
The agent token never touches disk — macOS Keychain only.
Related MCP server: personal-health-mcp
CLI (operator use)
healthcare init / record-vital / record-medication / record-activity / record-sleep / record-emotion / record-encounter / record-diagnosis-mention / create-medication-plan / create-reminder / edit-record / delete-record / export / backup / restore / daemon / pair-agent / grant-consent / verify-audit … — see healthcare --help.
License
Apache-2.0. This repository is the public engine extract of a private monorepo;
src/ and tests/ are carried over unchanged.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Governed personal world model and memory for your AI agent. Pair once, connect over MCP.
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Private health and fitness analytics through a secure remote MCP connection.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server that aggregates personal health data from Google Health, Oura, and Withings into a single, provider-attributed interface with configurable source of truth preferences.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server for querying multi-omic personal health data (genome, labs, wearables) with an honesty contract and progressive disclosure skills.1AGPL 3.0
- AlicenseCqualityBmaintenanceA local-first, model-agnostic MCP server that stores personal health data in a SQLite file and provides analysis-ready views for any AI client to log, retrieve, and reason over health records.79MIT