health4ai runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 21 Sep 2026.
Query your Apple Health data from your own Supabase/Postgres via local MCP.
Today is the operative word: we check health4ai every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add health4ai -- uvx health4ai
{
"mcpServers": {
"health4ai": {
"args": [
"health4ai"
],
"command": "uvx"
}
}
}
[mcp_servers.health4ai]
command = "uvx"
args = ["health4ai"]
{
"mcpServers": {
"health4ai": {
"args": [
"health4ai"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"health4ai": {
"args": [
"health4ai"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
DATABASE_URL (Postgres connection string for your Supabase project (transaction pooler; database password, not a service-role key).), HEALTHKIT_USER_ID (UUID of the Supabase Auth user whose HealthKit data to query.).
The author declared them in the registry entry; get the values from the project itself.
Your health data (weight, macros, weigh-ins) as MCP tools — in your own Supabase, zero custody.
Connect to your PostgreSQL database to query data and schemas.
MCP server for querying PostgreSQL databases
Connect to your Supabase database to query data and schemas.
Local-first bridge: export your own Mi Fitness (Xiaomi) health data to SQLite/JSON/CSV and MCP.
MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.
Extract database metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle.
PostgreSQL MCP — query databases, inspect schemas, explain queries.
Answers built from our own checks of this server.