I just built a MCP Server that connects Claude to all your wearables
Details
- External ID
- 47658617
- Source
- HN
- Company
- —
- Product
- I just built a MCP Server that connects Claude to all your wearables
- Website domain
- pacetraining.co
- Launched
- April 6, 2026
- Cohort
- —
- Upvotes
- 20
- Upvotes percentile
- 0.7506426735218509
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
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.
Enrichment
- Theme
- utilities for Claude and Claude Code
- Vertical
- Horizontal
- Function
- Agent / copilot
- Audience
- Developer
- AI stance
- AI-native
- Project type
- Hobby / open-source project
- Normalized one-liner
- mcp server connecting claude to wearables
- Manually corrected
- False
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 — 90 launches clear the similarity bar, closest 8 shown.
Attention rank: #30 of 91 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 156 days after the earliest competitor.
- AthleteData · hn · 2026-04-22 · 9 upvotes · similarity 0.47
- Claude Connectors · ph · 2026-04-26 · 443 upvotes · similarity 0.46
- Bluedot 2.1 · ph · 2026-05-27 · 373 upvotes · similarity 0.46
- freddy.health · ph · 2026-09-30 · 72 upvotes · similarity 0.44
- Red Grid Link · hn · 2026-03-20 · 54 upvotes · similarity 0.42
- Manufact: MCP Cloud for your Claude Connector & ChatGPT Plugin · yc · 2026-07-28 · 47 upvotes · similarity 0.42
- Get MCP Ads · ph · 2026-09-29 · 1 upvotes · similarity 0.41
- Pulse · hn · 2026-06-20 · 39 upvotes · similarity 0.39
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a agent / copilot tool for Agriculture yet.