How to Connect Apple Health to Claude: iPhone or Mac

Mac Connect

Connect checklist

Three checks, in order. Stop at the first one that fails. The iPhone path stays inside the Claude app. This list is the Mac MCP path for Claude Desktop, Claude Code, and Cursor.

1. Config snippet

Install and open the Health Data AI Analyzer Mac app first. Node.js 18+ has to be installed, because Claude starts health-analyzer-mcp with npx.

~/Library/Application Support/Claude/claude_desktop_config.json

Settings → Developer → Edit Config opens it. If the file is missing, create it.

{
  "mcpServers": {
    "health-analyzer": {
      "command": "npx",
      "args": ["-y", "health-analyzer-mcp"]
    }
  }
}

Already have other MCP servers? Do not paste a second { under the file. Add only the "health-analyzer" entry inside the existing mcpServers object. One root object, double quotes, no comments, no trailing commas.

claude mcp add health-analyzer -- npx -y health-analyzer-mcp

Cursor Settings → MCP. Same server entry:

{
  "mcpServers": {
    "health-analyzer": {
      "command": "npx",
      "args": ["-y", "health-analyzer-mcp"]
    }
  }
}

2. Health check

Quit the client completely and reopen it. Claude Desktop needs Cmd+Q, not a window close. Then confirm the Mac app is listening, and that the client loaded the tools.

The local API is http://localhost:8765, the same listener as http://127.0.0.1:8765. In the Mac app, open Settings and turn on Enable Local API for OpenClaw and scripts. The Local API section should show Running, with a dataset loaded.

GET /openclaw/status is public on loopback. It reports app version, whether a dataset is loaded, last import and sync timestamps, and available metrics. GET /status reports app and server version, dataset state, those timestamps, and the token path used by protected routes.

curl http://127.0.0.1:8765/openclaw/status
curl http://127.0.0.1:8765/status

The same paths work in a browser at http://localhost:8765/openclaw/status and http://localhost:8765/status. Connection refused means nothing is listening. That is an app or Local API problem, not an auth problem.

On the MCP side, the client should list the health-analyzer tools, including get_status. Ask it to call get_status. The tool takes no inputs and reports whether the local API is running and whether a dataset is loaded. In Claude Code, claude mcp list should include health-analyzer.

3. Failure states

Mac app not running, or the API is down. The curls above refuse the connection. Open Health Data AI Analyzer, load a dataset, and confirm Settings shows Local API Running. Curl again. Next doc: Apple Health Local API.

npx or Node is missing. In Terminal, node --version needs to be 18 or newer, and npx has to resolve. If Terminal sees Node but Claude does not, the GUI app is not using that PATH. The startup error is in ~/Library/Logs/Claude/. The first call can sit for several seconds while npx fetches health-analyzer-mcp. Claude Desktop only: skip Node by dragging the one-click extension (.mcpb) onto Claude Desktop. Server source: mcp-server on GitHub.

Claude Desktop config JSON is invalid. Claude ignores a config it cannot parse, so no tools appear and there is no API error. Usual causes: a second { pasted under an existing file, a trailing comma, or a comment. Keep a single JSON object. Re-copy the block above, or merge the one health-analyzer key into mcpServers, then Cmd+Q and reopen.

Tools still missing after restart. Closing the window does not reload MCP servers. Cmd+Q, reopen, and start a new chat. Claude Code: claude mcp list should show health-analyzer. If the process never starts, it is Node, PATH, or the JSON error above.

Auth or token errors. The server reads local-api-token.txt itself, from ~/Library/Application Support/Health Data AI Analyzer/local-api-token.txt. The sandboxed App Store build also searches ~/Library/Containers/com.rumjahn.healthkitanalyzer/Data/Library/Application Support/Health Data AI Analyzer/local-api-token.txt. "Token not found" or a 401 means that lookup failed. Call get_status — the response includes the paths it searched. If the file is there but unreadable, set HEALTH_ANALYZER_TOKEN or HEALTH_ANALYZER_TOKEN_FILE to the absolute path shown in app Settings. Do not put the token in the args array. GET /status returns the token path for protected HTTP routes. The MCP server attaches the token; Connect does not require hand-writing X-Health-Analyzer-Token.

Connect stops here. Use the Local API guide and the GitHub mcp-server tree. Need the full REST reference? That catalog is for after Connect works.