
Apple Health MCP Server
io.github.krumjahnPublished by GitHub account krumjahnv1.1.2Updated Oct 24, 2026
Apple Health data for Claude, Cursor, and any MCP client — 100% local on your Mac.
Overview
Local MCP server that gives an assistant access to your Apple Health data on a Mac, working entirely on-device.
- What you can do
- Connects an MCP client such as Claude or Cursor to Apple Health data stored on the same Mac.
- Works with a companion Mac app, the Health Data AI Analyzer, which generates a local API token the server uses.
- No tool list is published, so the exact queries the assistant can run are not documented here.
- All processing is described as staying local to the machine.
- When to use it
- Useful if you keep Apple Health data on a Mac and want an assistant to look at it without uploading it to a cloud service. Only relevant on macOS with the companion app installed.
- Requirements
- Runs as a local stdio process, installed from the npm package health-analyzer-mcp, so Node.js is needed. Requires the Health Data AI Analyzer Mac app, which writes a local API token; the server normally finds it automatically. Optionally set HEALTH_ANALYZER_TOKEN to supply the token directly, or HEALTH_ANALYZER_TOKEN_FILE to an absolute path of the app's local-api-token.txt. Desktop macOS only.
Installation
In SourceWeft
- Open Apple Health MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.1.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.