Skip to main content
Glama

⚡ One-command install with Delx Wellness for Hermes: npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.


0.8.0 release

Version 0.8.0 was published on 2026-11-02 and npm latest was verified at publication. Read the migration and compatibility notes before upgrading: HTTP network binds are restricted to loopback, imports/profiles have quotas, and corrected timestamps/cursor invalidation may change totals or replay records. For a pinned install, use npx -y samsung-health-mcp-unofficial@0.8.0.

Related MCP server: Zepp Life MCP

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y samsung-health-mcp-unofficial --http
# GET  http://127.0.0.1:3000/health
# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: SAMSUNG_HEALTH_MCP_HOST, SAMSUNG_HEALTH_MCP_PORT, SAMSUNG_HEALTH_MCP_TRANSPORT=http.

Unofficial local-first MCP server that reads Samsung Health personal-data CSV/ZIP exports and exposes them safely to AI agents.

Unofficial project. Not affiliated with, endorsed by, or supported by Samsung Electronics. Samsung Health is a trademark of Samsung Electronics. This package reads exports you generate yourself from the Samsung Health app.

No live Samsung Health cloud API. Samsung has Android SDK paths for partner apps, but this Node MCP does not log into Samsung, scrape accounts, or read Health Connect directly. It reads local exports now; a future Android bridge can sit beside it.

Built by David Mosiah as part of Delx Wellness, a registry of local-first wellness MCP connectors for Claude, Cursor, Hermes, OpenClaw and other MCP-compatible agents.

Why this exists

Samsung Health can collect high-signal wellness data from Galaxy Watch, Galaxy Ring and phones: steps, sleep, exercise, heart rate, oxygen saturation, body measurements and more. Samsung's official Health Data SDK can access many of these data types from Android apps with user permission, but distribution requires the Samsung app process and partnership flow. For a desktop MCP today, the reliable privacy-preserving path is a local personal-data download.

This connector reads that download locally, supports a folder of CSV files, a single CSV, or a zip containing CSV files, then exposes bounded summaries and records through MCP. No Samsung credentials, no OAuth token, no cloud proxy.

Setup In 60 Seconds

  1. On Android, export data from Samsung Health:

Samsung Health -> More options -> Settings -> Download personal data
  1. Transfer the downloaded Samsung Health folder or zip to this machine.

  2. Configure and verify:

npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth
npx -y samsung-health-mcp-unofficial doctor

Or let the CLI find the newest local Samsung Health export in Downloads, Desktop or Documents, copy it into managed local storage, and save that path:

npx -y samsung-health-mcp-unofficial setup --auto-import

Supported export paths:

  • /path/to/SamsungHealth/ or another folder containing CSV files

  • /path/to/samsung_health_export.zip

  • /path/to/com.samsung.health.step_count.csv

Then add this to your MCP client config:

{
  "mcpServers": {
    "samsung_health": {
      "command": "npx",
      "args": ["-y", "samsung-health-mcp-unofficial"]
    }
  }
}

For Claude Desktop, run setup --client claude --export-path /path/to/SamsungHealth and the snippet is written for you.

Keep it fresh — watch a folder (no Android device needed):

npx -y samsung-health-mcp-unofficial setup --watch-path /path/to/health-exports

Now every time you download personal data from the Samsung Health app and drop the new SamsungHealth folder (or its .zip, or any *samsung*health*.zip) into that folder, the connector auto-promotes the newest one to be the active export — on server startup and live while it runs — and refreshes the cached summaries. You can also trigger a re-scan on demand with the samsung_health_reimport tool. This is the cross-platform recurring-refresh path; a fully live Samsung Health sync still needs a native Android Health Connect bridge.

Try It With Your Agent

Use samsung_health_connection_status to check setup, then run samsung_health_daily_summary.
Give me a 5-line wellness brief for today.
Call samsung_health_data_inventory first. What Samsung Health signals and date ranges
are available in this export?
Call samsung_health_weekly_summary with response_format=json. Compare steps,
sleep, workouts and heart signals across the last 7 days.

Data Availability

The parser is intentionally flexible because Samsung personal-data downloads can vary by app version, locale and device. It infers record types from CSV filenames and headers.

Data

Available

Notes

Steps

yes

samsung_health_steps

Distance + active energy

yes

When present in CSVs or exercise rows

Heart rate + resting heart rate

yes

Galaxy Watch exports when available

HRV, respiratory rate, oxygen saturation

yes

Device and region dependent

Sleep + sleep stages

yes

Galaxy Watch sleep exports when available

Workouts / exercise

yes

Duration, distance, calories and activity type

Body weight + body fat

yes

When logged or synced

Live Health Connect read

no

Planned separate Android bridge

Samsung account login

no

Deliberately unsupported

Tools

Start with these:

  • samsung_health_connection_status - verify export path before reading data

  • samsung_health_data_inventory - discover available record types, date coverage, source count and stale export risk

  • samsung_health_daily_summary - daily wellness brief from export data

  • samsung_health_weekly_summary - weekly comparison and habit signals

Diagnostics:

  • samsung_health_capabilities

  • samsung_health_agent_manifest

  • samsung_health_privacy_audit

Records:

  • samsung_health_list_records - bounded records by type, start, end, limit

  • samsung_health_list_workouts - bounded workout records

Maintenance:

  • samsung_health_reimport - re-scan the watch folder (SAMSUNG_HEALTH_WATCH_PATH) and promote the newest export, refreshing summaries; pass check_only: true to preview without promoting

Prompts And Resources

Prompts:

  • samsung_health_daily_review

  • samsung_health_weekly_review

Resources:

  • samsung-health://capabilities

  • samsung-health://agent-manifest

  • samsung-health://inventory

  • samsung-health://summary/daily

  • samsung-health://summary/weekly

Privacy And Safety

  • Samsung Health exports are sensitive personal health data. Keep them local.

  • Never commit Samsung Health CSV/ZIP exports to GitHub, paste raw exports into chat, or upload them to issues.

  • The export path is read-only; the MCP never modifies your source export.

  • SAMSUNG_HEALTH_PRIVACY_MODE defaults to summary; raw record dumps are opt-in. It applies to every data path: samsung_health_list_records, samsung_health_list_workouts and samsung_health_daily_summary (which returns individual workout records only when privacy_mode is structured or raw).

  • samsung_health_weekly_summary accepts privacy_mode but always aggregates — a 30-day window of raw workouts is not what a weekly rollup is for. Rather than echoing back a mode it did not apply, the response carries requested_privacy_mode (what you asked for), privacy_mode (always summary, what was applied) and a privacy_disclosure naming the override. For record-level access use samsung_health_daily_summary or samsung_health_list_workouts.

  • Record and workout metadata is allowlisted, not denylisted. Only recognised wellness columns (times, durations, distances, calories, heart/sleep/body metrics, source names) leave the parser. GPS coordinates, altitude, deviceuuid and free-text user fields are dropped at parse time and never reach any tool, resource or raw response; a withheld_metadata_count field reports how many columns were dropped.

  • This is not medical advice. The server exposes data you exported yourself for personal AI workflows, not diagnosis or emergency monitoring.

Configuration

SAMSUNG_HEALTH_EXPORT_PATH=/path/to/SamsungHealth  # folder, csv, or zip
SAMSUNG_HEALTH_PRIVACY_MODE=summary                # summary | structured | raw
SAMSUNG_HEALTH_TIMEZONE=America/Fortaleza          # local-day summaries
SAMSUNG_HEALTH_WATCH_PATH=/path/to/health-exports  # optional: auto-reimport the newest export dropped here

setup writes these settings into ~/.samsung-health-mcp/config.json with 0600 permissions.

setup --auto-import scans common local folders for the newest Samsung Health export and copies it to ~/.samsung-health-mcp/exports/ with restrictive permissions. Fully live Samsung Health sync still requires a separate Android bridge.

Watch folder (recurring auto-reimport)

setup --watch-path <dir> (or SAMSUNG_HEALTH_WATCH_PATH) makes the connector treat a folder as a drop zone. On startup, while running (via filesystem events), and whenever the samsung_health_reimport tool is called, it promotes the newest Samsung Health export found there — a SamsungHealth export directory of CSVs, a single *.csv, or any *samsung*health*.zip — to be the active export and clears the snapshot + incremental caches so the next summary reflects the new data. samsung_health_connection_status reports the watch folder state and warns when a newer export is waiting. Fully live sync still requires a native Android Health Connect bridge.

Hermes / Remote Setup

npx -y samsung-health-mcp-unofficial setup --client hermes --export-path /path/to/SamsungHealth
npx -y samsung-health-mcp-unofficial doctor --client hermes
hermes mcp test samsung_health

After Hermes config changes, use /reload-mcp or hermes mcp test samsung_health. Don't restart the gateway for normal export access.

Development

git clone https://github.com/davidmosiah/samsung-health-mcp.git
cd samsung-health-mcp
npm install
npm test

Optional local HTTP transport:

SAMSUNG_HEALTH_MCP_TRANSPORT=http SAMSUNG_HEALTH_MCP_PORT=3000 node dist/index.js
curl http://127.0.0.1:3000/health

Official References


📧 Contact & Support

Skill or MCP

Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:

npx -y samsung-health-mcp-unofficial call samsung_health_connection_status --json '{}'

Copy skill/SKILL.md into your agent skills dir.

Available Tools

18 tools
samsung_health_agent_manifestSamsung Health Agent ManifestB
Read-onlyIdempotent

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

Inputs: client, response_format.

samsung_health_capabilitiesSamsung Health MCP CapabilitiesA
Read-onlyIdempotent

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

Inputs: response_format.

samsung_health_clear_incremental_cacheClear Samsung Health Incremental Import CacheA
DestructiveIdempotent

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).

Inputs: response_format, explicit_user_intent.

samsung_health_connection_statusSamsung Health Connection StatusA
Read-onlyIdempotent

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

Inputs: client, response_format.

samsung_health_daily_summarySamsung Health Daily SummaryA
Read-onlyIdempotent

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.

Inputs: date, timezone, privacy_mode, response_format.

samsung_health_data_inventorySamsung Health Data InventoryA
Read-onlyIdempotent

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

Inputs: end, start, timezone, privacy_mode, +1 more.

samsung_health_demoSamsung Health DemoA
Read-onlyIdempotent

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.

Inputs: response_format.

samsung_health_export_freshnessSamsung Health Export FreshnessA
Read-onlyIdempotent

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.

Inputs: response_format.

samsung_health_list_recordsList Samsung Health RecordsB
Read-onlyIdempotent

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

Inputs: end, type, limit, start, +3 more.

samsung_health_list_workoutsList Samsung Health WorkoutsB
Read-onlyIdempotent

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

Inputs: end, limit, start, privacy_mode, +1 more.

samsung_health_onboardingDelx Wellness Onboarding FlowA
Read-onlyIdempotent

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).

Inputs: locale, response_format.

samsung_health_privacy_auditSamsung Health Privacy AuditB
Read-onlyIdempotent

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

Inputs: response_format.

samsung_health_profile_getGet Delx Wellness ProfileA
Read-onlyIdempotent

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.

Inputs: response_format.

samsung_health_profile_updateUpdate Delx Wellness ProfileA

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.

Inputs: patch (required), response_format, explicit_user_intent.

samsung_health_quickstartSamsung Health QuickstartA
Read-onlyIdempotent

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.

Inputs: response_format.

samsung_health_reimportReimport Samsung Health Export from Watch FolderA
Idempotent

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.

Inputs: force, check_only, response_format.

samsung_health_weekly_summarySamsung Health Weekly SummaryA
Read-onlyIdempotent

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

Inputs: days, end_date, timezone, privacy_mode, +1 more.

samsung_health_wellness_contextSamsung Health Wellness ContextA
Read-onlyIdempotent

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

Inputs: date, notes, soreness, timezone, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation3/5

    The data-reading tools (list_records, list_workouts, data_inventory, export_freshness, daily/weekly_summary) are reasonably distinct, but the diagnostics/meta cluster (quickstart, capabilities, agent_manifest, connection_status, privacy_audit, demo) overlaps heavily—all answer variants of 'what does this connector do and is it set up?' An agent could easily pick capabilities when connection_status or quickstart was intended.

    Naming Consistency4/5

    Every tool uses the samsung_health_ prefix with snake_case, which is highly predictable. However, the suffixes mix verb_noun (list_records, profile_get) with bare nouns (capabilities, demo, agent_manifest, onboarding), so the pattern is prefix-consistent but not action-consistent.

    Tool Count3/5

    18 tools is on the heavy side for a local CSV/ZIP export reader, and a large share are informational/diagnostic (quickstart, demo, capabilities, manifest, connection_status, privacy_audit, onboarding, freshness) rather than data operations. The core data surface would justify ~10 tools, so the set feels padded.

    Completeness4/5

    Coverage is solid: record listing, workout listing, daily/weekly summaries, inventory, freshness, profile read/write, cache clearing and reimport all exist for the local-export domain. Minor gaps remain (no single-record fetch or record-type enumeration helper beyond inventory), but workflows have no real dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      A local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.
      26
      875 npm
      84
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server that provides local caching, sync, and tools for Zepp Life health data including steps, sleep, heart rate, workouts, and body measurements, supporting both file exports and cloud session access.
      10
      16
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local-first MCP server that reads Apple Health export files (export.xml/zip) and exposes activity, sleep, HRV, and workout data to AI agents, keeping all data on your machine.
      18
      191 npm
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.
      5
      MIT