---
title: Samsung Health MCP Server for AI Agents: Local Export Setup
description: Connect a Samsung Health personal-data export to an AI agent through a local-first MCP server and understand the boundary with Samsung Health Data SDK.
canonical: https://wellness.delx.ai/guides/samsung-health-mcp-for-ai-agents
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Samsung Health MCP Server for AI Agents

The Samsung Health MCP server reads a local personal-data folder, CSV file or ZIP and exposes bounded activity, sleep, heart, body and workout tools to an MCP-compatible agent. It does not log into a Samsung account from the MCP process.

## Short answer

Download your personal data inside Samsung Health, transfer the export to the agent machine, run <code>npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth</code>, and verify with <code>npx -y samsung-health-mcp-unofficial doctor</code>. This is not a live Samsung Health Data SDK bridge. Import a newer export when you want refreshed records.

## Connect Samsung Health MCP to Claude

Download the export, run the local setup and doctor commands, then add the <code>samsung_health</code> <code>mcpServers</code> block from the connector page to Claude Desktop. The MCP process reads the export path you control; it does not receive a Samsung account credential.

## Setup method

1. In Samsung Health on Android, open More options, Settings, Download personal data and Download.
2. Transfer the Samsung Health folder or ZIP to the computer or controlled server that runs the agent.
3. Run <code>npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth</code>. No Samsung account credential is required by the MCP process.
4. Run <code>npx -y samsung-health-mcp-unofficial doctor</code>, then call <code>samsung_health_connection_status</code>, <code>samsung_health_data_inventory</code> and <code>samsung_health_privacy_audit</code>.
5. Start with a daily or weekly summary. Generate and import a new export when fresher records are needed.

## MCP client configuration

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

## Data availability

- Steps and activity: available. Parsed from Samsung Health CSV filenames and headers.
- Heart rate, resting heart rate and HRV: available. When exported by the device/account.
- Sleep and sleep stages: available. When Galaxy Watch sleep records are present.
- Workouts and exercise records: available. Duration, distance, calories and activity type when exported.
- Body metrics: available. Weight and body-fat records when logged or synced.
- Live Health Connect or Samsung Health Data SDK reads: not_available. Planned as a separate Android bridge, not this Node MCP.

## Safe first-call sequence

1. <code>samsung_health_connection_status</code>
2. <code>samsung_health_data_inventory</code>
3. <code>samsung_health_capabilities</code>
4. <code>samsung_health_privacy_audit</code>
5. <code>samsung_health_daily_summary</code>

## Local export MCP versus Samsung Health Data SDK

This Node.js MCP connector reads a user-controlled export on a desktop or server. It is read-only by design and refreshes only when a newer export is imported.

Samsung Health Data SDK is the Android application path for selected, user-consented access to Samsung Health's data store. Samsung says the older Samsung Health SDK for Android was deprecated on July 31, 2025. Developer mode is for testing; app distribution and write access have separate partnership requirements.

## Privacy and limits

- No Samsung account credential is required.
- All parsing happens from a local folder, CSV file or zip.
- The agent sees bounded MCP responses, not the user's entire export by default.
- Summary mode is the default because Samsung Health exports are sensitive.
- Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.

- Not live Health Connect.
- Requires a manual export refresh.
- CSV columns can vary by app version, locale and device.

CSV names and columns can vary by Samsung Health version, locale, device and available records. This connector is not a continuous monitor.

## Official sources

- Download personal data: https://www.samsung.com/us/support/answer/ANS10001379/
- Samsung Health Data SDK: https://developer.samsung.com/health/data/overview.html
- SDK migration guide: https://developer.samsung.com/health/data/migration-guide/overview.html

## Canonical Delx sources

- Connector specification: https://wellness.delx.ai/connectors/samsung-health
- Connector comparison: https://wellness.delx.ai/guides/choose-wellness-mcp-connector
- Security model: https://wellness.delx.ai/security
- npm: https://www.npmjs.com/package/samsung-health-mcp-unofficial
- GitHub: https://github.com/davidmosiah/samsung-health-mcp

Delx Wellness and samsung-health-mcp-unofficial are not affiliated with Samsung. This is technical wellness integration context, not medical advice.