A
licenseA
qualityA
maintenanceAn MCP server that allows users to query and analyze their Apple Health data using SQL and natural language, utilizing DuckDB for fast and efficient health data analysis.
3
73 npm
571
MIT
MetricBridge (formerly Health Export AI)
by PhilipAD
Related Servers
Alternatives to MetricBridge (formerly Health Export AI)
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that enables LLMs to query Apple Health data such as steps, heart rate, sleep, and workouts via natural language, with secure cloud access through OAuth.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables seamless interaction between LLM-based agents and Apple Health data, allowing users to query, analyze, and manage health records through natural language commands.7278MIT
- AlicenseNot gradedqualityAmaintenanceRead-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.9Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI read-only access to Apple Health data through shortcuts and Cloudflare, enabling queries of current stats, detailed records, and trends.MIT
- AlicenseAqualityAmaintenanceHosted MCP server that syncs health data from Apple Health, Fitbit, Oura, and Google Health Connect, enabling Claude and ChatGPT to query workouts, sleep, nutrition, and recovery in plain English with interactive charts.732MIT
TDQS
A4.1/5.0
Scored across 16 tools
Disambiguation4/5
Most tools target clearly distinct operations (trends vs. arbitrary period comparison vs. correlation vs. bulk export vs. hourly intraday), and descriptions go to lengths to differentiate them. However, several tools overlap in the 'retrieve and analyze metrics' space — get_health_metrics, get_structured_export, and query_health_data (an explicit NL router) all return metric data, and get_mcp_status vs. get_freshness both report bridge health, so a few boundaries require careful reading.
Naming Consistency5/5
Names follow a highly predictable snake_case verb_noun pattern throughout: get_*, list_*, compare_*, correlate_*, query_*, resolve_*. Every name telegraphs its resource and action with no stylistic deviations.
Tool Count4/5
16 tools is on the heavier side but each maps to a legitimate facet of the health-export domain (metrics, trends, comparison, correlation, events, profile, workouts, sleep, cycle, status, freshness, resolution). It is slightly over the comfortable middle but nothing feels redundant enough to be cut.
Completeness5/5
The read-only bridge surface is unusually complete: discovery (list_metrics), retrieval at day and hourly granularity, aggregation, trends, arbitrary comparisons, correlation, name/unit resolution, plus contextual domains (events, profile, workouts, sleep, cycle) and data-trust tooling (status, freshness). No obvious lifecycle gaps remain for a read-only export bridge.
Maintenance
ActivityActive
ResponsivenessNo issues