Apple Health MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPLE_HEALTH_MCP_PORT | No | Port for HTTP transport (default 3000) | |
| APPLE_HEALTH_TIMEZONE | No | Timezone for local-day summaries (e.g., America/Fortaleza) | UTC |
| APPLE_HEALTH_WATCH_PATH | No | Optional directory to watch for new exports and auto-reimport | |
| APPLE_HEALTH_EXPORT_PATH | No | Path to Apple Health export file or folder (export.zip, export.xml, or apple_health_export/) | |
| APPLE_HEALTH_PRIVACY_MODE | No | Privacy mode: summary, structured, or raw | summary |
| APPLE_HEALTH_MCP_TRANSPORT | No | Transport type (e.g., http) for optional HTTP mode |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apple_health_agent_manifestB | Machine-readable install, runtime and privacy guidance for AI agents operating Apple Health export data. |
| apple_health_capabilitiesB | Explain supported Apple Health export data, unavailable live HealthKit access, privacy modes and recommended agent workflow. |
| apple_health_connection_statusA | Check local Apple Health export path, Node version, privacy mode and Hermes client posture without reading full export data. |
| apple_health_quickstartA | Personalized 3-step setup walkthrough for the human user. Adapts to current state (is APPLE_HEALTH_EXPORT_PATH set? does the export file exist and parse?). Call this first when the user asks 'how do I connect Apple Health?'. This connector is local-first and never touches Apple servers or cloud APIs. |
| apple_health_demoA | Returns realistic example payloads of apple_health_daily_summary, apple_health_weekly_summary, and apple_health_wellness_context with Apple-Watch-style values, so agents see the contract before parsing a real export. |
| apple_health_privacy_auditA | Return the local privacy and export-file posture without revealing health data. |
| apple_health_list_recordsA | List bounded records from a local Apple Health export.xml. Use type/start/end filters to keep output small. |
| apple_health_list_workoutsC | List bounded workout records from a local Apple Health export.xml. |
| apple_health_export_freshnessA | Check how recently the local Apple Health export file/directory was written. Returns mtime, days_since_export, an is_stale flag, and a recommendation. Considered stale if the export is older than 30 days, or older than 7 days with no recent records (the inventory's latest-record date is also older than 7 days). Use before relying on apple_health_daily_summary or apple_health_wellness_context to confirm the export is fresh. |
| apple_health_data_inventoryA | Scan the local Apple Health export once and report available record types, workouts, date coverage, freshness and safe next calls. |
| apple_health_daily_summaryA | Build a daily wellness summary from local Apple Health export data. It is not live HealthKit and not medical advice. |
| apple_health_wellness_contextB | Normalize local Apple Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines. |
| apple_health_weekly_summaryB | Build a weekly wellness summary from local Apple Health export data. It is not live HealthKit and not medical advice. |
| apple_health_profile_getA | Read the shared Delx Wellness profile from ~/.delx-wellness/profile.json. Returns preferred name, goals, devices, training/nutrition/exercise/agent preferences and safety flags. NEVER contains OAuth tokens or API secrets — this connector is local-export and has no cloud auth, but the profile contract is the same across every Delx Wellness MCP. Read-only. |
| apple_health_profile_updateA | Persist a partial patch to ~/.delx-wellness/profile.json. Requires explicit_user_intent=true (otherwise returns USER_ACTION_REQUIRED). Rejects secret-like fields (oauth, token, secret, password, cookie, refresh, api_key, session) at write time. Use to record preferred name, goals, devices, training context, nutrition context, exercise preferences, agent preferences, and safety flags. |
| apple_health_clear_incremental_cacheA | Manually clear the incremental import cache at ~/.apple-health-mcp/incremental-cache.json. The cache tracks the latest parsed timestamp per HealthKit category so subsequent |
| apple_health_reimportA | Re-scan the configured watch folder (APPLE_HEALTH_WATCH_PATH or |
| apple_health_onboardingA | Return the 11-question onboarding flow plus the current profile state and missing fields. Read-only — does NOT persist anything. Pair with apple_health_profile_update once the user answers. Cross-connector: the same profile is shared by every Delx Wellness MCP (whoop, garmin, oura, fitbit, strava, polar, withings, apple-health, samsung-health, google-health, nourish, cycle-coach, cgm, air). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| apple_health_daily_review | Review a day of Apple Health export data with non-medical wellness framing. |
| apple_health_weekly_review | Review a week of Apple Health export data with practical habit signals. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| apple_health_agent_manifest | Machine-readable install and operating instructions for AI agents. |
| apple_health_capabilities | Static capabilities, data boundary, privacy modes and recommended agent workflow. |
| apple_health_data_inventory_resource | Available record types, workouts, date coverage and data freshness for the configured export. |
| apple_health_daily_summary_resource | Daily Apple Health export summary for the current UTC day. |
| apple_health_weekly_summary_resource | Weekly Apple Health export summary for the current UTC week window. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/apple-health-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server