Samsung Health MCP
Related Servers
Alternatives to Samsung Health MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first MCP server that reads Apple Health export files (export.xml/zip) and exposes activity, sleep, HRV, and workout data to AI agents, keeping all data on your machine.18139 npm2MIT
- AlicenseBqualityAmaintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.26493 npm62MIT
- AlicenseAqualityAmaintenanceMCP server for the Google Health API: heart rate, activity, sleep, SpO2, HRV, ECG and irregular-rhythm notifications, read into a local SQLite cache for fast offline queries and trend analysis. OAuth 2.0 with automatic token refresh, incremental sync, a cache-only offline mode, and a doctor command that diagnoses a setup without spending quota.241,939 PyPIGPL 3.0
- AlicenseBqualityBmaintenanceMCP server that provides local caching, sync, and tools for Zepp Life health data including steps, sleep, heart rate, workouts, and body measurements, supporting both file exports and cloud session access.1011MIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server that aggregates personal health data from Google Health, Oura, and Withings into a single, provider-attributed interface with configurable source of truth preferences.MIT
- AlicenseAqualityDmaintenanceMCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.5MIT
TDQS
Scored across 18 tools
Several setup/discovery tools overlap: connection_status, privacy_audit, export_freshness, and data_inventory all report export/privacy posture, and list_records vs list_workouts has fuzzy boundaries. Core data tools are distinct and descriptions are detailed, but an agent could still select the wrong meta tool.
All tools use the samsung_health_ prefix with snake_case, but suffix styles are mixed: verb_noun names like list_records and profile_get coexist with bare nouns like capabilities, demo, quickstart, and onboarding. The shared prefix helps, but there is no consistent verb_noun pattern.
18 tools is on the heavy side, and several serve similar meta purposes such as manifest, capabilities, connection_status, privacy_audit, quickstart, and onboarding. Most tools have a role, but consolidation would make the set feel tighter.
The toolset covers local export reading, record listing, summaries, profile persistence, reimport, cache management, and onboarding. Minor gaps like no explicit export-path configuration tool and no single-record detail view are workable via existing setup guidance and filters.