Alex Honchar connects Garmin, Oura, Withings and Yazio to Claude to explore links between his diet, sleep and training, then saves the analysis as a reusable skill.
In this episode
- Connecting Garmin, Oura, Withings and Yazio to Claude
- Comparing diet, sleep and training data
- Generating dashboards when needed
- Managing credentials with local MCP servers
- Saving and scheduling recurring analyses
Timestamps
- 00:00 Cold open
- 00:32 Introduction and Alex's background in applied AI
- 01:25 The problem: your wearable data isn't connected to your AI
- 02:38 The setup: Garmin, Oura, Withings and Yazio connected via MCP
- 04:34 What is MCP? A plain-English explainer
- 06:37 Live demo: querying meals, workouts and sleep in natural language
- 10:56 Setting up your first connection (API keys and developer portals)
- 12:26 Security: why your credentials stay local with MCP
- 15:06 Cross-source analysis: how diet impacts sleep and performance
- 16:14 On-demand dashboards instead of maintained ones
- 17:32 The results: carbs, heavy eating days and sauna vs sleep quality
- 22:00 The top tip: be specific about what you ask for
- 23:01 Skills: codify your prompts, then schedule recurring analysis
- 26:04 Wrap-up and where to find Alex
Links
- Claude Code — the terminal-based agent Alex uses day to day
- Claude Cowork — the friendlier UI for the same workflows
- Garmin Connect — training, runs, heart rate, VO2 max
- Oura Ring — sleep, readiness, SpO2, stress (developer portal access token required)
- Withings — smart scale for weight and body composition (developer portal access token required)
- Yazio — meal and diet tracking
- Alex's step-by-step Medium guide and open-source skills marketplace — linked from the episode on YouTube
- Find Alex on LinkedIn and X for questions and requests
Disclaimers
- AI health analysis should complement, not replace, professional medical advice.
- Correlations in personal health data are indicative, not clinical findings.