google-health-mcp
Related Servers
Alternatives to google-health-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Fitbit/Google Health data (steps, sleep, heart rate, SpO2, workouts) and log weight, food, water, and exercises via natural language, self-hosted on Cloudflare Workers.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude, ChatGPT and Gemini to read wearable health data — daily activity, sleep stages, heart rate, SpO2, HRV, workouts, weight and nutrition — through a self-hosted, OAuth-protected Cloudflare Worker endpoint. It also lets users log weight, body fat, water, food, exercises, mood and symptoms by voice or chat, while leaving sensor-recorded data read-only.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access and analyze Fitbit health data (activity, sleep, heart rate, weight, profile) via natural language through the Fitbit Web API.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query personal health data collected by any wearable or phone fitness app through Android Health Connect or Apple Health, exposing read-only tools for metrics like heart rate, sleep stages, VO2 max, and body composition. It can run locally over USB with nothing stored, or be self-hosted on Cloudflare Workers with D1 to retain history beyond Health Connect's 30-day limit.20 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to read a user's WHOOP recovery, sleep, HRV, strain, and workout history through a local, read-only server with tools for today's status, personal baselines, sleep debt, trends, and period comparisons. It supports Claude Desktop, Claude Code, Codex, and GitHub Copilot, letting users ask natural-language questions about their health data without exporting it themselves.14 npm-
- AlicenseAqualityBmaintenanceEnables AI assistants to query read-only Fitbit and Pixel Watch health data through the Google Health API, including sleep, activity, heart rate, workouts, and profile information.745 npm1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct granularity: daily overview, per-day rollups, time-window rollups, raw points, GPS routes, devices, identity, and a data-type catalog. The only close pair is get_daily_rollup vs get_rollup, but both descriptions explicitly steer the caller ('Use get_daily_rollup for per-day values'), so misselection risk is low.
All names are snake_case and follow a clean list_/get_ verb_noun convention (list_data_types, get_daily_summary, get_exercise_route, etc.). The pattern is predictable and immediately signals read-only intent.
Eight tools is well-scoped for a read-only health data API: one catalog tool, three retrieval granularities, plus routes, devices, and profile. No tool appears redundant or padded.
The surface covers discovery, raw records, aggregation at two resolutions, daily summaries, GPS routes, paired devices, and user profile — essentially full read coverage of the Google Health API. Gaps are minor: no dedicated sleep-session query beyond raw data points, and no write operations (likely by API design).