A
licenseA
qualityA
maintenanceAn MCP server that allows users to query and analyze their Apple Health data using SQL and natural language, utilizing DuckDB for fast and efficient health data analysis.
3
73 npm
568
MIT
Health Export AI
by PhilipAD
Related Servers
Alternatives to Health Export AI
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that enables LLMs to query Apple Health data such as steps, heart rate, sleep, and workouts via natural language, with secure cloud access through OAuth.-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables seamless interaction between LLM-based agents and Apple Health data, allowing users to query, analyze, and manage health records through natural language commands.7269MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server that exposes Apple Health data (steps, workouts, sleep, etc.) from a local SQLite store, allowing AI agents to query health metrics without sending data to hosted services.7Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI read-only access to Apple Health data through shortcuts and Cloudflare, enabling queries of current stats, detailed records, and trends.MIT
- AlicenseAqualityAmaintenanceHosted MCP server that syncs health data from Apple Health, Fitbit, Oura, and Google Health Connect, enabling Claude and ChatGPT to query workouts, sleep, nutrition, and recovery in plain English with interactive charts.2732MIT
TDQS
A4.2/5.0
Scored across 14 tools
Disambiguation4/5
Most tools target clearly separate functions—listing, core queries, comparisons, exports, intraday, and singular domain areas like workouts or sleep. Minor boundary overlap exists between get_health_metrics/get_structured_export/query_health_data and between get_trends/compare_periods, but each has a distinct primary purpose that an agent can generally select by intent.
Naming Consistency5/5
All tools follow a consistent lowercase snake_case verb_noun pattern (get_, list_, compare_, correlate_, query_), with no exceptions. The verbs are specific and match the resource or action they perform, making the naming predictable and reliable.
Tool Count5/5
14 tools is well within the ideal 3-15 range for a domain-specific server. Each tool covers a meaningful aspect of health data export and analysis, and the count feels appropriately scoped rather than padded or trivially thin.
Completeness5/5
The tool surface comprehensively covers the promised health-export domain: metric discovery and retrieval, aggregations, trends, period comparisons, exports, intraday data, workouts, sleep, events, profile, cycle context, and even correlation. There are no obvious dead ends or missing operations that would block a reasonable health-data workflow.
Maintenance
ActivitySlowing
ResponsivenessNo issues