Nicheloom visits: 58,145 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

I just built a MCP Server that connects Claude to all your wearables

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hey HN,I built Pace, a Claude Connector that lets you connect all your wearables (Garmin, Polar, Whoop, 20+) with Claude.You connect your devices once and can analyze your data with Claude. No Dashboard needed, just in natural language. I already use it everyday, especially the visualization tool in Claude makes this really cool to use.Tools include: overview, sleep, training, activity, samples and trends.Tech Stack: Python (FastMCP), Google Cloud Run, Google Cloud SQL (PostgreSQL) and FirebaseIt is live and free to try (no Claude Pro/MAX Plan needed)..Would love feedback, especially from people who've built MCP servers or use wearables seriously.

HN · launched Apr 6, 2026 · 20 upvotes (top 25%) · 0 views

Niche: model context protocol tools · 465 launches, 13 in the last 7 days ▼ -24% · Explore this niche →

Category and tags

  • Horizontal
  • Agent / copilot
  • Developer
  • AI-native
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

Partial An MCP server wrapper is trivial to code, but integrating 20+ wearable hardware ecosystems requires commercial developer enterprise agreements, OAuth integrations, or paying for unified health aggregator APIs.

What it would actually take: Building a universal wearable bridge requires integrating with proprietary, gated APIs like Garmin Health, Polar AccessLink, and Whoop, which typically require registered business entities, enterprise compliance, and NDA agreements, or using an aggregator like Terra API or Vital. The system needs an OAuth token refresh service, normalized time-series data pipelines, and a Model Context Protocol (MCP) server layer exposing structured tool definitions for Claude. It demands enterprise API partner management and handling heterogeneous biometric time-series schemas.

Discussion

13 comments analyzed.

Competitors mentioned: Garmin MCP, TrainingPeaks MCP, Zepp (fitness app), Whoop, Withings

Concerns raised: Apple Watch and Mi Band not yet supported, Query performance with 90 days of sleep data, Rate limits on provider APIs (Garmin 25 req/15 min), Perceived latency in tool calls (300ms per call), Device connection issues

Feature requests: Apple Watch integration, Mi Band integration, Full workout trace exports, Combine data from multiple wearable devices in one account

Competitors

Other products that read as similar to this one : 159 launches clear the similarity bar, closest 8 shown.

Attention rank: #71 of 160 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 156 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.