Skip to main content
Glama

Related Servers

Alternatives to Health Access MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Lets Claude Code, Codex, and other AI assistants query locally collected Apple Health data, build weekly reports, check sync status, and log workouts or meals by hand.
      11
      MIT
    • 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
      260 npm
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Turns your own wearable data into coaching for hybrid fitness races by exposing readiness, running coach plans, fitness trends and training summaries as tools an agent can query. Keeps your data read-only at the provider and lets you log the station work and race profile your watch can't see in a local database.
      9
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read your own Apple Health data through a self-hosted SQLite mirror, allowing them to query health metrics, workouts, meals, and strength logs without sending data to the cloud.
      105 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query personal health data collected by any wearable or phone fitness app through Android Health Connect or Apple Health, exposing read-only tools for metrics like heart rate, sleep stages, VO2 max, and body composition. It can run locally over USB with nothing stored, or be self-hosted on Cloudflare Workers with D1 to retain history beyond Health Connect's 30-day limit.
      20 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading Apple Watch workouts and vitals from a local Health Access folder and writing validated training plans back into it as plain files, all through a local stdio MCP server with no account or network.
      336 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools occupy clearly distinct niches: get_workout (single session detail) vs list_workouts (compact rows) vs rate_workout (write effort) are separated by descriptions, and get_day/get_days/get_vitals differ in granularity. A few boundaries are soft — get_vitals overlaps with get_days for longitudinal trends, and list_ecgs overlaps with get_day's heart group — but an agent can reasonably choose.

    Naming Consistency4/5

    Nearly everything follows a clean verb_noun snake_case pattern (get_day, list_plans, push_plan, rate_workout). The single outlier is training_summary, which is a noun phrase with no verb, a minor deviation in an otherwise predictable scheme.

    Tool Count5/5

    Thirteen tools for a health-data server covering workouts, days, ECGs, plans, profile, vitals and summaries is well-scoped. Each tool maps to a distinct read or write need with no filler entries.

    Completeness3/5

    Read coverage is broad (days, workouts, ECGs, plans, profile, vitals, catalog) and writes exist for plans and effort ratings. However, list_ecgs advertises a voltage file but no tool retrieves ECG waveform data, and there is no way to delete or cancel a plan (only push_plan and get_plan_status), leaving dead ends in the lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues