Samsung Health Mcp
Point an MCP agent at Samsung Health personal-data CSV or ZIP exports for local summaries without sending vitals to a cloud API.
Overview
Samsung Health MCP is a Build-phase MCP server that ingests local Samsung Health CSV/ZIP exports so agents can query summaries with configurable privacy and timezone-aware daily stats.
What is this MCP server?
- Local-first parsing of Samsung Health personal-data folders, single .csv files, or .zip archives (v0.5.0)
- Privacy modes summary, structured, or raw via SAMSUNG_HEALTH_PRIVACY_MODE (default summary)
- Optional SAMSUNG_HEALTH_WATCH_PATH auto-promotes newest export on startup, live, and via samsung_health_reimport
- IANA timezone via SAMSUNG_HEALTH_TIMEZONE for daily and weekly local-day rollups
- No Samsung cloud OAuth—data stays on disk you control
- Server version 0.5.0
- 3 SAMSUNG_HEALTH_PRIVACY_MODE levels: summary, structured, raw
- stdio npm identifier samsung-health-mcp-unofficial
What problem does it solve?
Manually opening huge Samsung Health CSV dumps in spreadsheets breaks flow when you want an agent to answer “how did I sleep this week?”
Who is it for?
Builders who routinely export Samsung Health to disk and want private, API-key-free agent access on their own machine.
Skip if: Real-time sync from Samsung Cloud, multi-tenant hosted health backends, or regulated clinical pipelines without your own compliance layer.
What do I get? / Deliverables
After configuring an export path, your agent queries structured Samsung Health summaries locally with reimport when you drop a fresh export.
- Agent queries over parsed Samsung Health metrics
- Configurable response granularity (summary / structured / raw)
- Optional hot-reload of newest export from a watch directory
Recommended MCP Servers
Journey fit
Export parsing and agent tools belong in build when you integrate personal datasets into a product or automation. Samsung Health is a file-based external data source; integrations is the right catalog shelf for local-first MCP bridges.
How it compares
Local CSV/ZIP MCP bridge, not a Polar/Strava OAuth connector or a wellness coaching skill.
Common Questions / FAQ
Who is Samsung Health MCP for?
Solo builders and quantified-self tinkerers who use Samsung Health on phone or watch and export personal data for offline analysis with AI agents.
When should I use Samsung Health MCP?
Use it while building dashboards, habit coaches, or research notes where data must stay local and come from periodic Samsung exports.
How do I add Samsung Health MCP to my agent?
Register the npm stdio server samsung-health-mcp-unofficial, set SAMSUNG_HEALTH_EXPORT_PATH to your export folder or zip, and optionally SAMSUNG_HEALTH_WATCH_PATH for auto-reimport.