Health MCP
Related Servers
Alternatives to Health MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides read-only access to Withings health metrics including body composition, sleep, workouts, and ECG data with local SQLite caching and trend analysis. Features incremental synchronization, automatic OAuth token refresh, and supports all 200+ Withings measurement types for comprehensive health tracking.8100 PyPI1GPL 3.0
- AlicenseBqualityCmaintenanceEnables 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.48MIT
- AlicenseNot gradedqualityAmaintenanceEnables read-only exploration of WHOOP recovery, sleep, HRV, strain, workouts, and personal health analytics in AI assistants, with local dashboard and HYROX/triathlon readiness tools.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables reading personal activity, sleep, and health measurements, comparing weekly or monthly trends, and optionally saving food, water, mood, symptom, and menstrual-period records to Google Health through a self-hosted, owner-only deployment.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Oura Ring health and activity data, including sleep, readiness, activity, stress, SpO2, resilience, workouts, sessions, and heart rate via the Oura API v2.18 PyPIMIT
- AlicenseNot gradedqualityNot gradedmaintenanceExposes Apple Health data as three read-only MCP tools (now, detail, trends) for AI to query health metrics, sleep, and trends via HTTP.MIT
TDQS
Scored across 9 tools
The four lifting tools (sessions, summary, trend, breakdown) overlap conceptually: summary and breakdown both report volume by muscle/exercise, and trend vs summary can be confused for time-based questions. get_overview vs get_daily_checkin is also a close pair (all-metrics rollup vs single-day rollup), though the descriptions do draw the line. The rest (status, correlation, refresh_cache) are clearly distinct.
Every tool uses a consistent snake_case verb_noun pattern (get_*), with refresh_cache as the only non-get verb, which correctly signals its mutating side effect. Prefixing the lifting family with get_lifting_* makes the grouping obvious.
Nine tools is well within the sweet spot and each earns its place: one status/probe, one cache-control, and seven analytics/query tools covering sessions, aggregates, trends, breakdowns, correlations and rollups. Nothing looks like padding.
The surface is read-only: there is no way to write or log a session, meal or check-in, and raw weight/sleep/activity time series are only reachable aggregated through get_overview or get_daily_checkin. Lifting is covered thoroughly (sessions, summary, trend, breakdown), but sleep gets only a correlation tool and nutrition is absent entirely, so agents will hit dead ends for raw-series or write workflows.