Local-first MCP server that reads Samsung Health personal-data CSV/ZIP exports from the user's machine and exposes summaries and bounded records to AI agents. It does not use Samsung account login or live cloud access; it works on exported health data such as steps, sleep, heart rate, workouts, and body measurements.
From the registry: Unofficial local-first MCP server for Samsung Health personal-data CSV/ZIP exports.

$ npx -y samsung-health-mcp-unofficial setup --export-path <path-to-SamsungHealth-export>$ npx -y samsung-health-mcp-unofficial doctorPlease install the `samsung-health-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js** — Node.js is required to run the server via npx. (https://nodejs.org/)
- **Export Samsung Health personal data from Android** — In the Samsung Health app, export your personal data, then transfer the resulting folder, ZIP, or CSV file to the machine where the MCP server will run. (https://www.samsung.com/us/support/answer/ANS10001379/)
- **Initialize local server configuration** — Run setup once to save the Samsung Health export path into the server's local config. You can point to a folder of CSVs, a ZIP export, or a single CSV. Alternatively, use auto-import or watch-path setup. Run: `npx -y samsung-health-mcp-unofficial setup --export-path <path-to-SamsungHealth-export>`
Optional prerequisites:
- Verify setup — Optional but recommended diagnostic check after setup. Run: `npx -y samsung-health-mcp-unofficial doctor`
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","samsung-health-mcp-unofficial"]
- required environment variables:
- `SAMSUNG_HEALTH_EXPORT_PATH`: Path to the Samsung Health export source. Can be a folder containing CSV files, a ZIP export, or a single CSV file. Required in practice unless you already ran setup and stored this path in the local config file. (example: `<path-to-SamsungHealth-export>`)
- optional environment variables:
- `SAMSUNG_HEALTH_PRIVACY_MODE`: Privacy mode for responses. (example: `<summary|structured|raw>`)
- `SAMSUNG_HEALTH_TIMEZONE`: Timezone used for local-day summaries. (example: `<your-iana-timezone>`)
- `SAMSUNG_HEALTH_WATCH_PATH`: Optional watch folder to auto-reimport the newest Samsung Health export dropped there. (example: `<path-to-health-exports-folder>`)
Note: The README's primary install path is stdio via npx. The server can also run in an optional local HTTP transport for development using SAMSUNG_HEALTH_MCP_TRANSPORT=http and SAMSUNG_HEALTH_MCP_PORT, but the documented MCP client configuration uses stdio and no canonical HTTP endpoint URL is provided for client config. The setup command writes configuration to ~/.samsung-health-mcp/config.json, so env vars may be omitted if setup has already been run.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.SAMSUNG_HEALTH_EXPORT_PATHpath to the Samsung Health export folder, CSV, or ZIPSAMSUNG_HEALTH_PRIVACY_MODEcontrols whether output is summary, structured, or rawSAMSUNG_HEALTH_TIMEZONEtimezone used for local-day summariesSAMSUNG_HEALTH_WATCH_PATHoptional watch folder for auto-reimporting the newest exportMCP server for Gearsystem Sega Master System / Game Gear / SG-1000 emulator