Samsung Health MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAMSUNG_HEALTH_MCP_PORT | No | Port for HTTP transport, e.g., '3000'. | |
| SAMSUNG_HEALTH_TIMEZONE | No | Timezone for local-day summaries, e.g., America/Fortaleza. | |
| SAMSUNG_HEALTH_WATCH_PATH | No | Path to a folder to watch for new Samsung Health exports for auto-reimport. | |
| SAMSUNG_HEALTH_EXPORT_PATH | No | Path to Samsung Health export folder, CSV, or ZIP. | |
| SAMSUNG_HEALTH_PRIVACY_MODE | No | Privacy mode: summary, structured, or raw. | summary |
| SAMSUNG_HEALTH_MCP_TRANSPORT | No | Transport mode, e.g., 'http' for HTTP transport. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| samsung_health_agent_manifestB | Machine-readable install, runtime and privacy guidance for AI agents operating Samsung Health export data. |
| samsung_health_capabilitiesA | Explain supported Samsung Health export data, unavailable live Samsung Health access, privacy modes and recommended agent workflow. |
| samsung_health_connection_statusA | Check local Samsung Health export path, Node version, privacy mode and Hermes client posture without reading full export data. |
| samsung_health_quickstartA | 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_demoA | 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_privacy_auditB | Return the local privacy and export-file posture without revealing health data. |
| samsung_health_list_recordsB | List bounded records from local Samsung Health CSV/ZIP export data. Use type/start/end filters to keep output small. |
| samsung_health_list_workoutsB | List bounded workout records from local Samsung Health CSV/ZIP export data. |
| samsung_health_export_freshnessA | 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_context to confirm the export is fresh. |
| samsung_health_data_inventoryA | Scan the local Samsung Health export once and report available record types, workouts, date coverage, freshness and safe next calls. |
| samsung_health_daily_summaryA | Build a daily wellness summary from local Samsung Health export data. It is not live Samsung Health and not medical advice. |
| samsung_health_wellness_contextA | Normalize local Samsung Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines. |
| samsung_health_weekly_summaryA | Build a weekly wellness summary from local Samsung Health export data. It is not live Samsung Health and not medical advice. |
| samsung_health_profile_getA | 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_updateA | 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_clear_incremental_cacheA | 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_reimportA | Re-scan the configured watch folder (SAMSUNG_HEALTH_WATCH_PATH or |
| samsung_health_onboardingA | 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| samsung_health_daily_review | Review a day of Samsung Health export data with non-medical wellness framing. |
| samsung_health_weekly_review | Review a week of Samsung Health export data with practical habit signals. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| samsung_health_agent_manifest | Machine-readable install and operating instructions for AI agents. |
| samsung_health_capabilities | Static capabilities, data boundary, privacy modes and recommended agent workflow. |
| samsung_health_data_inventory_resource | Available record types, workouts, date coverage and data freshness for the configured export. |
| samsung_health_daily_summary_resource | Daily Samsung Health export summary for the current UTC day. |
| samsung_health_weekly_summary_resource | Weekly Samsung Health export summary for the current UTC week window. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/samsung-health-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server