apple-health-mcp
Provides an MCP server (usable via npx) that lets an MCP client query locally exported Apple Health data from CSV files using natural-language-to-SQL plus direct SQL execution, with schema introspection and automated health reporting. Uses DuckDB for in-process analytics, with lazy loading by time windows and result caching via TTL.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Likely local-only usage with no explicit auth; this reduces exposure over the network but increases the importance of securing the host and MCP client connection. No TLS/auth/scoping guidance is documented. The project uses DuckDB and @modelcontextprotocol/sdk; no dependency vulnerability data is provided, so hygiene is estimated. Health data is sensitive; ensure exported CSVs and any cache/temp files are protected and not shared unintentionally.
⚡ Reliability
Best When
You have Apple Health data already exported to CSV locally and want an AI assistant to query it on your machine via MCP.
Avoid When
You need network-accessible, authenticated healthcare data access for others, or you require documented operational/SLA guarantees and strong security controls beyond local tooling.
Use Cases
- • Ask questions about Apple Health metrics (e.g., heart rate trends, activity summaries) in natural language
- • Run targeted SQL queries against exported Apple Health CSV data
- • Generate periodic weekly/monthly health summaries or reports
- • Explore the available schema/tables for Apple Health export datasets
Not For
- • Handling live Apple Health data directly from an iOS device
- • Serving as a multi-user remote API for sensitive health data without additional infrastructure/security controls
- • Use cases requiring strict compliance guarantees (HIPAA/GDPR) without documented compliance posture
Interface
Authentication
No authentication mechanism is described in the README; access appears to rely on local environment execution and MCP client connectivity.
Pricing
No pricing information provided; appears to be an open-source npm package intended for local use.
Agent Metadata
Known Gotchas
- ⚠ Relies on Apple Health CSV export naming/table conventions; table names are lowercase in some contexts.
- ⚠ “No data found” can occur if CSVs are not in the expected directory or time window.
- ⚠ Large datasets may hit memory limits; use MAX_MEMORY_MB and/or shorter time windows.
- ⚠ Since it executes SQL, agents should be careful to constrain queries by date ranges to avoid heavy scans.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for apple-health-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.