health-export-mcp 1.4.0 → 1.4.1

package/README.md

@@ -31,6 +31,11 @@ It's an MCP server that turns your Apple Health export into a tool your AI agent
 - **What it isn't:** a cloud service. There's no developer server in the path — your data goes only where *you* point it.
 - **Setup:** point the server at your exported data and add it to your AI client.
 
+> **Just exported and the Mac has not seen it yet?** iCloud can take a few minutes to sync the
+> file across, so a check 60 seconds after tapping Run in the app can still show the old
+> timestamp. `get_mcp_status` reports `lastDataDate` and the intraday `lastWrite`, which is the
+> quickest way to tell "still syncing" from "never arrived".
+
 > **Try it with no iPhone needed:** `node server.mjs --demo` serves a deterministic synthetic dataset (400 days, workouts, events, sleep sessions) with every answer watermarked as synthetic. Or run `npm test` to write a sample cache and exercise every tool.
 
 ---

package/manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.3",
   "name": "health-export-ai",
   "display_name": "Health Export AI",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "Query your Apple Health data, exported by the Health Export AI iOS app to iCloud Drive, from any MCP agent. Local-first, read-only, zero dependencies.",
   "long_description": "A zero-dependency MCP server that exposes 190 Apple Health metrics (exported by the Health Export AI iOS app into an iCloud Drive folder) to any MCP-compatible agent: Claude Desktop, opencode, Cursor, OpenClaw, Hermes. No bridge, no Docker, no HTTP receiver: the server reads the synced cache file directly over stdio. 14 tools: get_mcp_status, list_metrics, get_health_metrics, get_trends, compare_periods, get_structured_export, get_intraday, query_health_data, list_events, get_profile, get_workouts, get_sleep_sessions, get_cycle_context, correlate_metrics. Plus 22 MCP prompts and a --demo mode with a synthetic dataset. Get the companion iOS app on the App Store: https://apps.apple.com/app/id6784185201",
   "author": {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "health-export-mcp",
   "mcpName": "io.github.PhilipAD/health-export-mcp",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "type": "module",
   "description": "Open-source, zero-dependency Model Context Protocol (MCP) server to query Apple Health / HealthKit data (190 metrics) from Claude, ChatGPT, Cursor, OpenClaw, Hermes and any MCP agent.",
   "keywords": [

package/receiver.mjs

@@ -23,7 +23,7 @@ import fs from 'node:fs';
 import path from 'node:path';
 import os from 'node:os';
 import net from 'node:net';
-import { pathToFileURL } from 'node:url';
+import { fileURLToPath } from 'node:url';
 
 const WS_GUID = '258EAFA5-E914-47DA-95CA-C5AB0DC85B11';
 const MAX_BODY = 64 * 1024 * 1024;
@@ -232,7 +232,16 @@ function encodeTextFrame(str) {
   return Buffer.concat([header, payload]);
 }
 
-// Standalone run (also importable by server.mjs). pathToFileURL handles spaces in the path.
-if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+// Standalone run (also importable by server.mjs). Both sides are resolved to REAL paths: a bin
+// symlink (npx, npm i -g) otherwise makes this false and the receiver silently never starts.
+const isEntryPoint = (() => {
+  if (!process.argv[1]) return false;
+  try {
+    return fs.realpathSync(process.argv[1]) === fs.realpathSync(fileURLToPath(import.meta.url));
+  } catch {
+    return false;
+  }
+})();
+if (isEntryPoint) {
   startReceiver();
 }

package/server.json

@@ -6,13 +6,13 @@
     "url": "https://github.com/PhilipAD/health-export-mcp",
     "source": "github"
   },
-  "version": "1.4.0",
+  "version": "1.4.1",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "health-export-mcp",
-      "version": "1.4.0",
+      "version": "1.4.1",
       "transport": {
         "type": "stdio"
       }

package/server.mjs

@@ -15,13 +15,13 @@
 // INSTEAD of the protocol loop, so their stdout is theirs to print to.
 
 import fs from 'node:fs';
-import { pathToFileURL } from 'node:url';
+import { fileURLToPath } from 'node:url';
 import * as store from './healthstore.mjs';
 import * as ev from './events.mjs';
 import { PROMPTS } from './prompts.mjs';
 import { DEMO } from './demo.mjs';
 
-const SERVER = { name: 'health-export-ai', version: '1.4.0' };
+const SERVER = { name: 'health-export-ai', version: '1.4.1' };
 const DEFAULT_PROTOCOL = '2025-06-18';
 const log = (...a) => process.stderr.write('[mcp] ' + a.join(' ') + '\n');
 
@@ -487,7 +487,20 @@ function serveStdio() {
 
 // Importable on purpose (tests read TOOLS/SERVER; a future embedder reads handle): the protocol
 // loop and the CLI run only when this file IS the entry point, mirroring receiver.mjs.
-const IS_MAIN = process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href;
+// `npx pkg` and `npm i -g pkg` BOTH invoke the bin through a SYMLINK, so process.argv[1] is the
+// link (…/node_modules/.bin/health-export-mcp) while import.meta.url is the real file. Comparing
+// the two directly made this false under npx: the protocol loop never started, the process exited
+// 0 with no stdout and no stderr, and an MCP client saw only "connection closed" ~700 ms in.
+// Reported 2026-08-19 by a user whose client failed four times in a row, working only when he
+// bypassed the shim with a direct `node …/server.mjs`. Resolve BOTH sides to real paths.
+const IS_MAIN = (() => {
+  if (!process.argv[1]) return false;
+  try {
+    return fs.realpathSync(process.argv[1]) === fs.realpathSync(fileURLToPath(import.meta.url));
+  } catch {
+    return false;          // argv[1] deleted mid-flight, or an unreadable path: not the entry point
+  }
+})();
 if (IS_MAIN) {
   const argv = process.argv.slice(2);
   if (argv.includes('--help') || argv.includes('-h')) {