Skip to main content
Glama
Sign In
Samsung Health MCP

Samsung Health MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Samsung Health MCP

No user-submitted related servers found.

    Related Servers

    • Apple Health MCP

      davidmosiah
      A
      license
      A
      quality
      B
      maintenance
      Local-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.
      18
      367 npm
      3
      MIT

    • Google Health MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      A 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.
      26
      586 npm
      75
      MIT

    • google-health-mcp

      partymola
      A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      24
      184 PyPI
      1
      GPL 3.0

    • Zepp Life MCP

      kubulashvili
      A
      license
      B
      quality
      C
      maintenance
      MCP 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.
      10
      15
      MIT

    • personal-health-mcp

      adamconde
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-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

    • google-health-mcp-server

      madfreakz
      A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation3/5

    The data-reading tools (list_records, list_workouts, data_inventory, export_freshness, daily/weekly_summary) are reasonably distinct, but the diagnostics/meta cluster (quickstart, capabilities, agent_manifest, connection_status, privacy_audit, demo) overlaps heavily—all answer variants of 'what does this connector do and is it set up?' An agent could easily pick capabilities when connection_status or quickstart was intended.

    Naming Consistency4/5

    Every tool uses the samsung_health_ prefix with snake_case, which is highly predictable. However, the suffixes mix verb_noun (list_records, profile_get) with bare nouns (capabilities, demo, agent_manifest, onboarding), so the pattern is prefix-consistent but not action-consistent.

    Tool Count3/5

    18 tools is on the heavy side for a local CSV/ZIP export reader, and a large share are informational/diagnostic (quickstart, demo, capabilities, manifest, connection_status, privacy_audit, onboarding, freshness) rather than data operations. The core data surface would justify ~10 tools, so the set feels padded.

    Completeness4/5

    Coverage is solid: record listing, workout listing, daily/weekly summaries, inventory, freshness, profile read/write, cache clearing and reimport all exist for the local-export domain. Minor gaps remain (no single-record fetch or record-type enumeration helper beyond inventory), but workflows have no real dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources