Interrogate your iPhone health data with SQL

What it does apple-health-mcp is a local Model Context Protocol server that reads Apple Health CSV exports and exposes them to MCP clients such as Claude Desktop. It loads your exported tables into an in-memory DuckDB instance, then offers tools for schema discovery, read-only SQL queries, and periodic health summaries. Everything stays on your machine; the server never makes network requests.

The interesting bit Rather than wrestling with Apple’s native XML export format, the server expects the simpler CSV layout produced by the third-party Simple Health Export CSV app and translates that directly into a temporary in-memory database. That keeps the parser small and the setup lightweight, though it locks you into a specific export workflow.

Key highlights

• Runs fully offline with no cloud dependency or data upload
• Loads complete export history into memory with no artificial date windows
• Exposes three tools: health_schema for exploration, health_query for SQL, and health_report for summaries
• Requires CSV exports from the Simple Health Export CSV iPhone app; native Apple Health XML is unsupported
• Memory footprint is roughly 1 GB per two years of data, capped by a configurable MAX_MEMORY_MB limit

Caveats

• The DuckDB database is rebuilt from scratch on every server launch, so each startup reloads all CSVs from disk
• Device overlap in exports can produce duplicate-looking measurements; queries need to filter by sourceName when appropriate
• Exports that exceed the configured memory limit fail explicitly rather than spilling to disk

Verdict Ideal for quantified-self enthusiasts who already use Simple Health Export CSV and want to interrogate years of health metrics through an MCP client. Skip it if you need native Apple Health XML support or a persistent database that survives process restarts.