private · 3 sources · read-only by default
Health MCP
My health data lives in three apps that don’t talk to each other: sleep and activity in Google Health, meals in Lose It!, and weigh-ins on a Wyze scale. This is a private MCP server that hands all of it to my AI agent, so one question gets one answer.
Ask “how’s the cut going?” and it checks body composition, the week’s sleep and steps, and the food diary, then answers in a sentence.
MCP · Google Health API · Lose It! · Wyze
What it does
- Daily and weekly summaries of sleep, steps, heart rate, and activity
- Day-by-day rollups of one metric over any date range
- Weight and body fat from the scale
- Calories and macros from the food diary
- Logs a custom food in two steps: a preview, then a one-time confirm
Views
How it’s built
Three sources
Google Health has sleep, heart rate, steps, and workouts. The Wyze scale’s weigh-ins land in Google Health too, so weight and body fat come from there. Lose It! has the food diary and daily macros.
An allowlist, not a firehose
Every tool names the metrics it can read: sleep, heart rate, resting heart rate, steps, active minutes, active zone minutes, distance, exercise, calories, weight, and body fat. Nothing else in Google Health is reachable.
Summaries first
The daily and weekly tools return privacy-structured rollups, not raw records. When I need detail, I ask for one metric by name.
One careful write
Logging a food takes two calls. The first returns a preview and a short-lived, single-use token. The second needs that token, an explicit confirm, and an idempotency key. If a write’s outcome is unclear, it isn’t retried, so nothing gets logged twice.
Things I ask it
- How did I sleep this week compared to last?
- Am I on pace for 10k steps today?
- Log 6 oz grilled chicken for lunch.
Links
Questions? [email protected]