Health · Local MCP server
health4ai
Query your Apple Health data from your own Supabase/Postgres via local MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jefflitt1/health4ai- Version
- 0.1.0
- Status
- Active
- Category
- health
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- jefflitt1 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jefflitt1) · how
- Listed under
- PostgreSQL MCP servers, Supabase MCP servers
- Website
- health4.ai
- Repository
- github.com/jefflitt1/health4ai (folder mcp-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | health4ai | 0.1.0 | stdio |
How to connect health4ai
health4ai runs locally from a Python package published to PyPI: health4ai version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx health4ai. It reads these environment variables: DATABASE_URL (required, secret) and HEALTHKIT_USER_ID (required); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"health4ai": {
"command": "uvx",
"args": [
"health4ai"
],
"env": {
"DATABASE_URL": "<secret>",
"HEALTHKIT_USER_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Health IntelHealthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement. | Remote · HTTPLive check: ✓ handshake |
| Health OSN-of-1 health experiments in your AI assistant: Oura/RescueTime data, protocols, workouts. | Remote · HTTPLive check: sign-in required |
| Health PartnerManage your Health Partner account, log food, water, workouts, body using agent. | Remote · HTTPLive check: sign-in required |
| health-osLocal-first personal health record: labs, meds, wearables, food log, deterministic safety checks. | Local · stdio |
| Healthcare DataUS healthcare data for AI agents: CMS, FDA adverse events, CDC, NPPES NPI. Keyless, real samples. | Remote · HTTPLive check: ✓ handshake |
| Healthcare Fda Intelligence MCPScrape the FAA Aircraft Registry by N-number - aircraft make, model, year, owner name, address, airw. | Remote · HTTPLive check: ✗ no handshake |
| Healthcare Provider IntelligenceProvider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance. | Remote · SSELive check: sign-in required |
| Healthclaw GuardrailsGuardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. | Remote · HTTPLive check: sign-in required |