Skip to main content
Glama
Sign In
Apple Health AI Bridge MCP Server

Apple Health AI Bridge MCP Server

by roian6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Apple Health AI Bridge MCP Server

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      Object-Orient
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that exposes Garmin Connect health data from a local SQLite database to AI assistants, enabling queries for recent days, sleep, weekly trends, and a guarded SQL query surface.
      MIT

    • 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

    • Vital Relay

      bulbasas
      A
      license
      Not graded
      quality
      C
      maintenance
      A remote MCP server that lets AI assistants such as Claude, ChatGPT, and any MCP client ask about a user's Apple Health data, with answers produced live by the user's iPhone via HealthKit. Health data is forwarded through process memory only — never written to disk — and covers sleep, workouts, metric series, health overviews, and user-defined custom metrics.
      AGPL 3.0

    • 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
    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.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly different resources or metadata layers, but get_bridge_status and explain_sources overlap on sync/provenance, and get_bridge_context_markdown is a composite view that can blur with bridge status. Descriptions do help separate them.

    Naming Consistency5/5

    All tool names use consistent snake_case with a clear verb_noun pattern (get_, list_, explain_) throughout the set. No mixing of conventions or vague action names.

    Tool Count5/5

    Nine tools is well-scoped for a read-only health-data bridge; each covers a distinct resource or metadata layer without obvious bloat. The count sits comfortably in the ideal 3-15 range.

    Completeness4/5

    The surface covers bridge status/context, supported and synced metric metadata, timeseries, workouts, sleep, daily summaries, and source provenance, which is strong for a read-only bridge. Minor gaps like sync-control or deeper per-activity detail exist, but no critical dead ends for the stated read-only purpose.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources