apple-health-mcp vs Leo-Health-Core
Local Apple Health data tools compared
apple-health-mcp lets an MCP-connected assistant query supported Apple Health CSV exports with DuckDB. Leo-Health-Core imports Apple Health exports and Whoop CSVs into SQLite, with terminal and local web dashboards; the main difference is assistant-driven querying versus a broader local import and viewing workflow.

apple-health-mcp: Query Apple Health Data with DuckDB
apple-health-mcp is a local-first MCP server built on DuckDB that lets AI assistants query Apple Health CSV exports with SQL and generate health summaries. It is designed for people who want to explore their own health data through an MCP client.

Leo-Health-Core: Unify Apple Health and Whoop Data Locally
Leo-Health-Core is a Python tool that parses Apple Health exports and Whoop CSVs into a normalized SQLite database. It keeps health data on your machine and provides a terminal view, local dashboard, and automatic import watcher.
| apple-health-mcp | Leo-Health-Core | |
|---|---|---|
| Language | TypeScript | Python |
| License | MIT | MIT |
| Stars | 576 | 94 |
| Forks | 24 | 9 |
| Last analyzed | Oct 24, 2026 | Oct 15, 2026 |
Key differences
- apple-health-mcp supports the Simple Health Export CSV layout, while Leo-Health-Core parses Apple Health export ZIPs and imports Whoop CSV data.
- apple-health-mcp exposes schema discovery, SQL queries, and health reports through MCP tools; Leo-Health-Core provides normalized SQLite tables, dashboards, and an automatic import watcher.
- apple-health-mcp is written in TypeScript and uses DuckDB, while Leo-Health-Core is written in Python and uses SQLite.
- Both projects use the MIT license; apple-health-mcp has 576 stars and 24 forks, while Leo-Health-Core has 94 stars and 9 forks.
- apple-health-mcp reads CSV files in place and loads each table's history into memory; Leo-Health-Core imports files into a persistent database and documents Docker Compose support.
- apple-health-mcp is active with recent commits and releases, while Leo-Health-Core is marked quiet, with no commits in the last 90 days despite a release in the past year.
Choose apple-health-mcp if you…
- want an MCP-connected assistant to query Apple Health CSV data using SQL and generate summaries.
- need local-first analysis with schema discovery and configurable weekly, monthly, or custom reports.
- work with the Simple Health Export CSV layout and can account for its memory and process-isolation considerations.
Choose Leo-Health-Core if you…
- want to combine Apple Health export data with Whoop records in normalized SQLite tables.
- need a terminal or local web dashboard, or automatic imports watched from the Downloads folder.
- prefer a Python tool with documented Docker support and can review and test changes given its quiet recent development.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.