Skip to main content
Glama
Sign In
Apple Health MCP

Apple Health MCP

by daveremy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Apple Health MCP

No user-submitted related servers found.

    Related Servers

    • Apple Health AI Bridge MCP

      roian6
      A
      license
      A
      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.
      9
      30
      Apache 2.0

    • Apple Health Chat MCP

      gh33k
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude to answer natural language questions about your Apple Health data by analyzing local CSV exports, supporting metrics like steps, heart rate, sleep, and more.
      6
      2
      MIT

    • health-db

      JeiKeiLim
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to query and explore self-hosted Apple Health data, including daily metrics, time series, workouts, ECG records, heart notifications, sleep sessions, trends, freshness, and schema resources through authenticated streamable HTTP.
      MIT

    • MetricBridge (formerly Health

      PhilipAD
      A
      license
      A
      quality
      A
      maintenance
      Open-source MCP server for MetricBridge (formerly Health Export AI). 16 tools and 22 prompts let any MCP agent query 190 Apple Health metrics from files on your own machine. The server is read-only, has zero dependencies and makes zero network calls.
      22
      1,214 npm
      11
      MIT

    • apple-health-semantic-mcp

      Barbaroso
      A
      license
      A
      quality
      D
      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
    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

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: daily summary, trends over a range, and workouts. However, apple_health_daily and apple_health_trends overlap significantly in metrics (steps, HR, HRV, sleep), which could cause confusion about when to use each. The descriptions help clarify, but some ambiguity remains.

    Naming Consistency5/5

    All tool names follow a consistent apple_health_* pattern with clear, descriptive suffixes (daily, trends, workouts). This predictable naming makes it easy for agents to understand the tool set and infer purposes without confusion.

    Tool Count3/5

    With only 3 tools, the server feels thin for the Apple Health domain, which typically includes more operations like adding data, querying specific metrics, or managing permissions. While it covers basic retrieval, the scope seems limited compared to the potential complexity of health data.

    Completeness2/5

    The tool set is severely incomplete for an Apple Health server, focusing only on retrieval of daily summaries, trends, and workouts. There are no tools for creating, updating, or deleting health data, nor for accessing detailed metrics or settings, which are common in health APIs. This will likely cause agent failures in broader health management tasks.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources