Query Apple Health data using natural language and SQL.
Apple Health MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Query Apple Health data using natural language and SQL.
Query Apple Health data from an MCP client using SQL and DuckDB. The server runs locally, reads CSV exports on demand, and provides tools for schema discovery, read-only queries, and health summaries.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once Apple Health MCP is connected, these are the calls the assistant has available:
health_schema — Discover table names, columns, units, and sample rowshealth_query — Run a read-only SELECT query with JSON, CSV, or summary outputhealth_report — Generate a weekly, monthly, or custom health summaryYou will need one environment variable: HEALTH_DATA_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
export.xml format is not currently supported.Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Apple Health MCP's toolset — health_schema, health_query, health_report — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| health_schema | Discover table names, columns, units, and sample rows |
| health_query | Run a read-only SELECT query with JSON, CSV, or summary output |
| health_report | Generate a weekly, monthly, or custom health summary |
{
"mcpServers": {
"apple-health": {
"command": "npx",
"args": ["-y", "@neiltron/apple-health-mcp"],
"env": {
"HEALTH_DATA_DIR": "/path/to/your/unzipped/health-export"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
export.xml format is not currently supported.| Variable | Description | Required |
|---|---|---|
| HEALTH_DATA_DIR | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.