Provider guide · local export MCP
Samsung Health MCP server for AI agents
Turn a user-controlled Samsung Health export into bounded Galaxy Watch activity, sleep, heart, body and workout context for an MCP-compatible agent.
Short answer
Download a local personal-data export from Samsung Health, transfer the folder or ZIP to the agent machine, run npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth, and verify with npx -y samsung-health-mcp-unofficial doctor. This connector is not a live Samsung Health Data SDK bridge: it reads the export you control and must be refreshed when you want newer records.
Choose the local export MCP when
- A Galaxy Watch or Samsung Health archive is already the source of truth.
- The agent runs on a desktop or controlled server rather than inside Android.
- No Samsung account credential should enter the MCP process.
- Daily and weekly summaries are sufficient between manual export refreshes.
Choose an Android SDK path when
- Your own Android app needs user-consented live access to the Samsung Health data store.
- You need an app-distribution path governed by Samsung partnership requirements.
- You need supported write operations rather than a read-only local archive workflow.
- The workflow requires continuous monitoring or clinical use; this MCP is neither.
Setup method
Connect Samsung Health to an agent in five checks
- 1
Download your personal data
In Samsung Health on Android, open More options, then Settings, Download personal data and Download. Finish the in-app account confirmation and wait for the export.
- 2
Move the export to the agent machine
Transfer the Samsung Health folder or ZIP to the computer or controlled server that will run the MCP process. Treat it as sensitive health data.
- 3
Run local setup
Run npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth. The connector records a local path and defaults to summary mode; it does not receive a Samsung account password or cloud token.
- 4
Verify before asking for records
Run npx -y samsung-health-mcp-unofficial doctor, then call samsung_health_connection_status, samsung_health_data_inventory and samsung_health_privacy_audit.
- 5
Start bounded and refresh deliberately
Ask for a daily or weekly summary first. Generate and import a new export when the user wants fresher data; do not describe the file as a live feed.
Install and verify
npx -y samsung-health-mcp-unofficial setup --export-path /path/to/SamsungHealth
npx -y samsung-health-mcp-unofficial doctorMCP client configuration
{
"mcpServers": {
"samsung_health": {
"command": "npx",
"args": ["-y", "samsung-health-mcp-unofficial"]
}
}
}What the export can provide
Activity
Steps, distance and active energy when matching CSV records are present.
Sleep
Sleep intervals and stages when the Galaxy Watch export includes them.
Heart and body
Heart rate, resting heart rate, HRV, weight and body-fat fields when exported.
Workouts
Activity type, duration, distance and calories from exported exercise records.
Safe first-call sequence
- 1. samsung_health_connection_status
- 2. samsung_health_data_inventory
- 3. samsung_health_capabilities
- 4. samsung_health_privacy_audit
- 5. samsung_health_daily_summary
Privacy boundary
No Samsung account credential is required by the connector. Parsing happens from a local folder, CSV or ZIP, and summary mode is the default. Give the MCP process access only to the export directory it needs.
Local MCP versus Samsung's Android SDK
This MCP connector
Node.js process for desktops and servers. Reads a user-downloaded archive, stays local, is read-only by design and refreshes when a newer export is imported.
Samsung Health Data SDK
Android application SDK 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, while distribution and writes have partnership requirements.
Samsung Health MCP questions
What is the Samsung Health MCP server?
samsung-health-mcp-unofficial is a local parser for a Samsung Health personal-data folder, CSV file or ZIP. It exposes bounded activity, sleep, heart, body and workout tools to MCP-compatible agents without logging into a Samsung account from the MCP process.
How do I connect Samsung Health MCP to Claude?
Download a Samsung Health personal-data export, run samsung-health-mcp-unofficial setup with its local export path, run doctor, then add the samsung_health mcpServers block from the connector page to Claude Desktop. The setup uses the local export; it does not put a Samsung account credential in Claude or the MCP process.
Does Samsung Health MCP read live Galaxy Watch data?
No. This connector reads a local personal-data export. It is not a live Samsung Health Data SDK bridge, Health Connect reader or continuous monitor. Create and import a newer export when the agent needs refreshed records.
Does the MCP server need my Samsung account credential?
No Samsung account credential is stored or requested by the MCP server. Samsung may ask you to sign in inside the Samsung Health app while generating the personal-data download; only the resulting local export is passed to the connector.
When should a developer use Samsung Health Data SDK instead?
Use Samsung Health Data SDK when you are building an Android application that needs user-consented access to the Samsung Health data store. Samsung says the older Samsung Health SDK for Android was deprecated on July 31, 2025. Distribution and write access have separate partnership requirements.
Is Samsung Health MCP medical advice?
No. The connector provides personal fitness and wellness context. It is not medical advice, diagnosis, treatment, emergency monitoring or a replacement for a qualified clinician.
Canonical and official sources
Delx Wellness and samsung-health-mcp-unofficial are not affiliated with Samsung. This page provides technical wellness integration context, not medical advice.