Apple Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_SIZE | No | Number of cached query results | 100 |
| MAX_MEMORY_MB | No | Maximum memory usage in MB | 1024 |
| HEALTH_DATA_DIR | Yes | Path to your Apple Health CSV export directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_queryB | Run one analytical query on Apple Health data. |
| health_reportB | Generate structured health reports for a specific period |
| health_schemaA | Get information about available health data tables, their structure, and sample data to help write SQL queries |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_summary | Summarize the most recent week of health data: activity, heart rate, sleep, and workouts |
| sleep_analysis | Analyze sleep duration, stages, and consistency over a recent period |
| workout_progress | Review workout frequency, duration, and trends over a recent period |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Health data schema | Tables, columns, units, sample rows, and query tips for the loaded export |
| Available tables | Every queryable table in the export with its load state and row count |
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: health_query runs analytical queries, health_report generates reports, and health_schema provides metadata about tables. There is no overlap in functionality.
All tools follow a consistent pattern with the prefix 'health_' followed by a clear noun (query, report, schema). Naming is uniform and predictable.
With only 3 tools, the set is compact but well-scoped for the stated analytical purpose. While slightly minimal, each tool earns its place and doesn't feel overly sparse.
The tools cover the essential analytical workflow: querying data, generating reports, and understanding schema. Minor gaps exist (e.g., no direct data export), but for the apparent read-only analytical scope, coverage is sufficient.