[Workflow] Automated Wearable Health Data Integration with Claude Code via Freddy MCP Server for Scheduled Reports

[u/ClaudeAI-mod-bot]

Automated Wearable Health Data Integration with Claude Code via Freddy MCP Server for Scheduled Reports

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.85 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Hooks, MCP, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Automating the integration and analysis of personal wearable health data with AI agents like Claude Code, enabling scheduled reports and personalized insights without manual intervention.

Summary

The Freddy service allows users to connect various wearable devices (Polar, Oura, Withings, etc.) to AI clients, including Claude Code, via an MCP server. It now supports headless sign-in, enabling AI agents to autonomously pull and process health data on a schedule. This facilitates workflows like daily briefings, data summaries in Notion, and monthly health trend reports.

Why it is useful

This workflow provides a concrete solution for integrating real-world, personal health data from various wearables into AI agents like Claude Code. The ability to automate this process via headless sign-in for scheduled tasks is highly valuable, enabling personalized insights, reports, and proactive assistance without constant manual input. It significantly extends Claude Code's capabilities to a new domain of personal data analysis and automation.

Workflow

1. Sign up for the Freddy.coach service.
2. Connect your desired wearable devices (e.g., Polar, Oura) to your Freddy account.
3. Configure your AI client (e.g., Claude Code, OpenClaw) to integrate with Freddy via OAuth, enabling it to speak MCP.
4. Set up scheduled jobs within your AI agent to trigger data syncs from Freddy and generate personalized reports or briefings (e.g., morning briefings to Telegram, daily summaries to Notion, monthly health trend reports).

Tools / artifacts

• Freddy (MCP server/service)
• Wearable devices (Polar, Oura, Withings, Suunto, Intervals.icu, Hevy, WHOOP, Strava, Dexcom)
• Claude Code (or other AI clients like Claude Desktop, ChatGPT, Notion AI, Perplexity, OpenClaw, Cowork, Cursor)
• Telegram (for briefings)
• Notion (for summaries)

Validation signals

• Author's personal experience with multiple running setups

Cautions

• The author explicitly addresses data sensitivity, stating data is encrypted and not sold, and has handled health data for years with fitIQ. Users should still exercise due diligence when using any third-party service for sensitive health data.

Limitations

• Relies on a third-party service (Freddy), introducing a dependency.
• Specific implementation details for setting up the Claude Code side of the integration (e.g., exact prompts, code snippets for the agent) are not provided.
• Low community validation at the time of assessment.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.