Machine-readable install, runtime and privacy guidance for AI agents operating Samsung Health export data.

Explain supported Samsung Health export data, unavailable live Samsung Health access, privacy modes and recommended agent workflow.

Check local Samsung Health export path, Node version, privacy mode and Hermes client posture without reading full export data.

Personalized 3-step setup walkthrough for the human user. Adapts to current state (is SAMSUNG_HEALTH_EXPORT_PATH set? does the export folder/CSV/zip exist and parse?). Call this first when the user asks 'how do I connect Samsung Health?'. This connector is local-first and never touches Samsung, Health Connect, or any cloud API.

Returns realistic example payloads of samsung_health_daily_summary, samsung_health_weekly_summary, and samsung_health_wellness_context with Galaxy-Watch-style values, so agents see the contract before parsing a real export.

Return the local privacy and export-file posture without revealing health data.

List bounded records from local Samsung Health CSV/ZIP export data. Use type/start/end filters to keep output small.

List bounded workout records from local Samsung Health CSV/ZIP export data.

Check how recently the local Samsung Health export directory/CSVs were written. Returns mtime, days_since_export, an is_stale flag, and a recommendation. Considered stale if the export is older than 30 days, or older than 7 days with no recent records (the inventory's latest-record date is also older than 7 days). Use before relying on samsung_health_daily_summary or samsung_health_wellness_context to confirm the export is fresh.

Scan the local Samsung Health export once and report available record types, workouts, date coverage, freshness and safe next calls.

Build a daily wellness summary from local Samsung Health export data. Individual workout records follow privacy_mode (default summary: aggregates only). It is not live Samsung Health and not medical advice.

Normalize local Samsung Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines.

Build a weekly wellness summary from local Samsung Health export data. It is not live Samsung Health and not medical advice.

Read the shared Delx Wellness profile from ~/.delx-wellness/profile.json. Returns preferred name, goals, devices, training/nutrition/exercise/agent preferences and safety flags. NEVER contains OAuth tokens or API secrets — this connector is local-export and has no cloud auth, but the profile contract is the same across every Delx Wellness MCP. Read-only.

Persist a partial patch to ~/.delx-wellness/profile.json. Requires explicit_user_intent=true (otherwise returns USER_ACTION_REQUIRED). Rejects secret-like fields (oauth, token, secret, password, cookie, refresh, api_key, session) at write time. Use to record preferred name, goals, devices, training context, nutrition context, exercise preferences, agent preferences, and safety flags.

Manually clear the incremental import cache at ~/.samsung-health-mcp/incremental-cache.json. The cache tracks the latest parsed timestamp per Samsung Health record category so subsequent samsung_health_list_records calls (with incremental_cache: true) skip already-seen records. Use this when you want to force a full re-parse without changing the export file. The cache also auto-invalidates when the export file mtime changes. Gated by explicit_user_intent: true (requires explicit user intent to wipe local cache).

Re-scan the configured watch folder (SAMSUNG_HEALTH_WATCH_PATH or setup --watch-path <dir>) for a newer Samsung Health export. If a newer SamsungHealth folder / .csv / samsunghealth.zip is found, it is promoted to the active export, the in-memory snapshot cache and incremental cache are cleared, and subsequent summaries reflect the new data. With check_only=true, only report what would happen without promoting. This is the cross-platform recurring-refresh path — the native Android Health Connect bridge needs an Android device and is separate. Requires explicit user intent when promoting a new export (force or non-check_only); check_only is read-only inspection.

Return the 11-question onboarding flow plus the current profile state and missing fields. Read-only — does NOT persist anything. Pair with samsung_health_profile_update once the user answers. Cross-connector: the same profile is shared by every Delx Wellness MCP (whoop, garmin, oura, fitbit, strava, polar, withings, apple-health, samsung-health, google-health, nourish, cycle-coach, cgm, air).