MCP.Market

Samsung Health MCP server

by davidmosiah·io.github.davidmosiah/samsung-health-mcp·v0.5.0·18 stars
No reviews yet

Unofficial local-first MCP server for Samsung Health personal-data CSV/ZIP exports.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

18 stars241 downloads/wk

Reviews

Write one

Nobody has reviewed Samsung Health yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Samsung Health tools (18, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • samsung_health_agent_manifest

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

  • samsung_health_capabilities

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

  • samsung_health_clear_incremental_cache

    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 whe

  • samsung_health_connection_status

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

  • samsung_health_daily_summary

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

  • samsung_health_data_inventory

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

  • samsung_health_demo

    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.

  • samsung_health_export_freshness

    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_contex

  • samsung_health_list_records

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

  • samsung_health_list_workouts

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

  • samsung_health_onboarding

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

  • samsung_health_privacy_audit

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

  • samsung_health_profile_get

    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.

  • samsung_health_profile_updatewrite action

    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.

  • samsung_health_quickstart

    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.

  • samsung_health_reimport

    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 / *samsung*health*.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 happe

  • samsung_health_weekly_summary

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

  • samsung_health_wellness_context

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

Public scan report

scanner v0.1.10 · 2026-11-10 · same rubric, same numbers if you re-run it

no findings
  • Code scan58 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Samsung Health compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 93% of 48,114 servers
Tools
18
the typical server has 7
Tools that change things
6%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
18
more than 90% of 28,851 servers
Downloads a week
241
more than 72% of 15,093 servers with a package

What its tools let an agent do: 17 read · 1 change

Install Samsung Health in Claude Code, Cursor or VS Code

Runs npx -y samsung-health-mcp-unofficial on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add samsung-health-mcp -- npx -y samsung-health-mcp-unofficial
Add to Cursor

What the publisher says

From the Samsung Health repository's README, as published. We do not edit it. Read it on GitHub

<!-- delx-wellness header v2 --> Samsung Health MCP

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

⚡ One-command install with Delx Wellness for Hermes:

npx -y delx-wellness-hermes setup &mdash; preconfigures this connector and the other 8 in a dedicated Hermes profile.

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

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: SAMSUNGHEALTHMCPHOST, SAMSUNGHEALTHMCPPORT, SAMSUNGHEALTHMCP_TRANSPORT=http.

<!-- /delx-wellness header v2 -->

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Samsung Health: common questions

Is Samsung Health MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Samsung Health safety report
How do I install Samsung Health?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Samsung Health need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is Samsung Health maintained?
The last commit was 10 days ago (2026-11-05). The latest release is v0.5.0.
How does Samsung Health compare with other MCP servers?
safety score 92/100 (higher than 93% of 48,114 servers); tools 18 (the typical server has 7); tools that change things 6% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from davidmosiah →