An MCP server that provides Apple Health data via the Health Auto Export app for iOS
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"health-auto-export-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This project provides examples of how to work with the TCP server in Health Auto Export app for iPhone/iPad.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.
FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.
MCP Security Weekly
Get CVE alerts and security updates for Health Auto Export Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This project provides examples of how to work with the TCP server in Health Auto Export app for iPhone/iPad.
You can make queries to the server directly over TCP, or the project can be connected to LLMs, such as Claude app for desktop, via MCP.
In the /docs folder you will find more detailed instructions.
Clone the repository:
git clone <repository-url>
cd health-auto-export-mcp-server
Install dependencies:
npm install
Configure .env file:
.env.example file and rename it to .envHAE_HOST (your device IP address)Build the project:
npm run build
Run dev server:
npm run dev
client_example.ts provides an example of a client that connects to the Health Auto Export server over TCP.
npm run buildnode ./dist/client_example.jsFor MCP tool names and breaking changes in 1.0.0, see CHANGELOG.md. Implementation lives in src/server.ts.
Build the project using npm run build
Navigate to Settings -> Developer -> Edit Config
This should open claude_desktop_config.json
Add the MCP server details as shown below, pointing to the correct path on disk where you have set up this project:
{
"mcpServers": {
"health_auto_export": {
"command": "node",
"args": ["/Users/username/Desktop/hae-mcp/dist/server.js"]
}
}
}
Restart Claude Desktop
Keep in mind Claude's context window limitations when using MCP. This means data may need to be aggregated appropriately in order to process requests.
Further information on Claude Desktop MCP configuration