Skip to main content
Glama
roian6

Apple Health AI Bridge MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_bridge_statusA

Read-only redacted bridge and receiver sync status for local agents; omits sample values, cursor values, and token material; no clinical interpretation.

get_bridge_context_markdownA

Read-only redacted Markdown bridge context for local agents/wiki; omits sample values, cursor values, token material, and clinical interpretation.

list_supported_timeseries_typesB

Read-only supported timeseries type metadata; metadata only, no local health values, no cursor values, and no clinical interpretation.

list_synced_metricsA

Read-only catalog observation listing synced metric types, provenance, and missing-data caveats; no clinical interpretation.

get_timeseriesA

Read-only time-series observations for selected metric types with source provenance and missing-data caveats; no clinical interpretation.

get_workoutsA

Read-only workout observations for a date range with source provenance and missing-data caveats; no clinical interpretation.

get_sleep_summaryB

Read-only sleep-stage summary observations for a date range with source provenance and missing-data caveats; no clinical interpretation.

get_daily_summaryB

Read-only daily observation summaries for a date range with source provenance, missing-data caveats, sum-safe sample_totals, and type-aware sample_statistics for non-summable metrics; no clinical interpretation.

explain_sourcesB

Read-only provenance summary for local sources and sync cursors with missing-data caveats; no clinical interpretation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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
ResponsivenessResponsive