Skip to main content
Glama
burakdirin

apple-health-export-mcp

by burakdirin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apple-health-export-mcp

No user-submitted related servers found.

    Related Servers

    • Apple Health MCP

      davidmosiah
      A
      license
      A
      quality
      A
      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
      221 npm
      2
      MIT

    • apple-health-semantic-mcp

      Barbaroso
      A
      license
      A
      quality
      B
      maintenance
      Query Apple Health export data with an LLM via a semantic layer that avoids common data traps, enabling accurate natural-language queries about health metrics. Optionally imports CPAP therapy data for correlation.
      3
      MIT

    • Apple Health MCP

      daveremy
      A
      license
      B
      quality
      C
      maintenance
      Enables users to query Apple Health metrics, workouts, and trends from CSV files exported via the Health Auto Export app. It allows MCP clients to analyze health data such as heart rate, sleep stages, and activity levels directly from local iCloud Drive storage.
      3
      5 npm
      1
      MIT

    • vitals-mcp

      DevSrijit
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to query locally computed recovery, strain, sleep, workout, and heart-rate data from a personal SQLite database, with tools for daily and sleep summaries, workout details, heart-rate buckets, schema inspection, reports, sync, and read-only SQL.
      8
      MIT

    • Apple Health AI Bridge MCP

      roian6
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that exposes Apple Health data (steps, workouts, sleep, etc.) from a local SQLite store, allowing AI agents to query health metrics without sending data to hosted services.
      7
      Apache 2.0
    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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_quantity aggregates numeric metrics, get_sleep handles sleep stages, get_workouts summarizes workouts, list_sources lists devices, and list_types enumerates health metrics. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., get_quantity, list_sources). There is no variation in style or convention.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a health data export interface. Each tool serves a distinct purpose without redundancy, and the count is neither too sparse nor too heavy.

    Completeness5/5

    The tool surface covers key health data access: numeric metrics (get_quantity), sleep (get_sleep), workouts (get_workouts), source discovery (list_sources), and type discovery (list_types). This set supports common queries without obvious gaps for the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources