Samsung Health Mcp

Samsung Health MCP

Read your Samsung Health CSV/ZIP exports — activity, sleep, heart, stress — locally.
Local-first MCP server — tokens never leave your machine.

[npm version] [npm downloads] [License MIT] [Site]

[GitHub stars] [Built for MCP] [Hermes one-command setup] [Samsung Health]

⚡ 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 [email protected].

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

2. Transfer the downloaded Samsung Health folder or zip to this machine.

3. Configure and verify:

npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealthnpx -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 rangesare 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.

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 zipSAMSUNG_HEALTH_PRIVACY_MODE=summary                # summary | structured | rawSAMSUNG_HEALTH_TIMEZONE=America/Fortaleza          # local-day summariesSAMSUNG_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/SamsungHealthnpx -y samsung-health-mcp-unofficial doctor --client hermeshermes 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.gitcd samsung-health-mcpnpm installnpm test

Optional local HTTP transport:

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

Official References

• Samsung personal-data export: https://www.samsung.com/us/support/answer/ANS10001379/
• Samsung Health Data SDK: https://developer.samsung.com/health/data/overview.html
• Samsung Health Data SDK app process: https://developer.samsung.com/health/data/process.html
• Android Health Connect: https://support.google.com/android/answer/12201227

Links

• npm: https://www.npmjs.com/package/samsung-health-mcp-unofficial
• Docs site: https://wellness.delx.ai/connectors/samsung-health
• GitHub: https://github.com/davidmosiah/samsung-health-mcp
• Delx Wellness registry: https://github.com/davidmosiah/delx-wellness

📧 Contact & Support

• 📨 [email protected] — general questions, integration help, partnerships
• 🐛 Bug reports / feature requests — GitHub Issues
• 🐦 Updates — @delx369 on X
• 🌐 Site — wellness.delx.ai

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.