Apple Health Mcp Server

What is Apple Health Mcp Server?

A Model Context Protocol (MCP) server designed for interaction between LLM-based agents and Apple Health data. It provides a standardized interface for querying, analyzing, and managing health records imported from XML exports and indexed in Elasticsearch, accessible from MCP-compatible clients like Claude Desktop.

How to use Apple Health Mcp Server?

Export Apple Health data as an XML file, clone the repository, set environment variables in config/.env, and run make es to start Elasticsearch and import the data. Configure the server in your MCP client using either Docker (mcp-server:latest with appropriate mounts) or local uv run start with the correct binary path, then restart the client.

Key features of Apple Health Mcp Server

• Built on the FastMCP framework for high-performance MCP server capabilities
• Imports, parses, and analyzes Apple Health XML exports
• Powerful search and filtering using natural language and advanced parameters
• Elasticsearch integration for scalable indexing and querying
• Modular tools for structure analysis, record search, type extraction, and statistics
• Container-ready with Docker support for easy deployment

Use cases of Apple Health Mcp Server

• Analyze available health data types and their volume from an XML export
• Query daily, weekly, or monthly activity statistics using natural language
• Search and filter specific health records by type, device, or attribute value
• Summarize and compare workout trends across different time periods
• Generate trend analyses for a health record type over daily, weekly, monthly, or yearly aggregations

FAQ from Apple Health Mcp Server

What is this server and how does it differ from directly querying Apple Health?

It provides an MCP interface for LLM agents to interact with Apple Health data without requiring knowledge of XML or Elasticsearch query languages. Data is indexed in Elasticsearch for fast, scalable search and aggregation.

What are the runtime requirements and dependencies?

Requires Docker (recommended) or uv with Docker, an Apple Health XML export, and an Elasticsearch instance running locally. Environment variables are configured via a .env file.

Where is my health data stored and processed?

Data is extracted from the Apple Health XML export file and indexed into a local Elasticsearch instance. The server itself runs locally and does not send data to external services by default.

What transport and authentication mechanisms are supported?

The server uses the Model Context Protocol (MCP) for communication. Authentication is configured via environment variables for Elasticsearch (ES_USER, ES_PASSWORD), and the server is intended for local use with a personal MCP client.

Are there any known limitations?

XML tools are still being optimized for performance, and more advanced Elasticsearch analytics features are planned. Large XML exports may require significant system resources during import.