Connect your Garmin, Polar, Oura, Withings, Intervals.icu, Hevy, WHOOP, Suunto, Concept2 and more to ChatGPT, Claude, Claude Code, or any AI that speaks MCP. Sleep, recovery, HRV, workouts, queryable in natural language.
the MCP part is what gives me pause here, more than the wearable integration itself. sleep, HRV and recovery numbers going through a general-purpose chat history is a different privacy surface than the wearable's own closed app, that data can end up in logs, in a provider's training pipeline (depending on settings), or just sitting in a chat transcript someone else on a shared account could open. is there a local-only mode where the MCP server never round-trips through a hosted layer, or does every query pass through freddy's own backend before the AI sees it?
Querying sleep and HRV in plain language through an MCP client is a neat angle, since most wearable apps still make you read dashboards. I'm building a voice AI that calls aging parents every day, and the thing we keep hitting is how to turn noisy signals into something a family member would actually act on. How do you decide when freddy. should surface a trend unprompted versus waiting for the user to ask?
About freddy.health on Product Hunt
“talk to your body in Claude, ChatGPT, Muse, or any other AI”
freddy.health launched on Product Hunt on September 30th, 2026 and earned 72 upvotes and 7 comments, placing #35 on the daily leaderboard. Connect your Garmin, Polar, Oura, Withings, Intervals.icu, Hevy, WHOOP, Suunto, Concept2 and more to ChatGPT, Claude, Claude Code, or any AI that speaks MCP. Sleep, recovery, HRV, workouts, queryable in natural language.
freddy.health was featured in Health & Fitness (83.4k followers), Wearables (182.8k followers) and Artificial Intelligence (481.5k followers) on Product Hunt. Together, these topics include over 167.9k products, making this a competitive space to launch in.
Who hunted freddy.health?
freddy.health was hunted by Tom Tomaszewski. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how freddy.health stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Tom Tomaszewski
the MCP part is what gives me pause here, more than the wearable integration itself. sleep, HRV and recovery numbers going through a general-purpose chat history is a different privacy surface than the wearable's own closed app, that data can end up in logs, in a provider's training pipeline (depending on settings), or just sitting in a chat transcript someone else on a shared account could open. is there a local-only mode where the MCP server never round-trips through a hosted layer, or does every query pass through freddy's own backend before the AI sees it?