OSS Tanbou
View on GitHubProject website

normalize wearable health data behind one API, webhooks, and MCP

OSS scale score Not calculatedOSS health 100
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
2,586
Primary language
Python
License
MIT
Repository last updated
Sep 29, 2026
On this page

Overview

Open Wearables unifies data from Garmin, Oura, Whoop, Apple Health, and other providers into a common model exposed through REST APIs, webhooks, a developer portal, and an MCP server.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Normalize health data across wearable providers

Sleep, activity, workouts, heart rate, and related measurements can be consumed through a provider-independent model.

Sources: [2]

Integrate applications and AI through webhooks and MCP

Applications can receive webhooks for new data, while LLMs and agents can query the same data through MCP.

Sources: [2]

Best fit

Fits products that need several wearable integrations behind one backend

It reduces duplicated OAuth, data-mapping, and sync work across provider APIs.

Sources: [2]

Before adoption

Pin stable release images for production

The README recommends official images pinned to a stable release rather than nightly or main-branch builds.

Sources: [2][3]

Sensitive health data requires explicit security and privacy controls

Self-hosting does not remove the need to design credential storage, access control, retention, backups, and AI data exposure.

Sources: [2][4]

Official sources

  1. [1]the-momentum/open-wearables repository(2026-09-30)
  2. [2]Open Wearables README(2026-09-30)
  3. [3]Open Wearables 0.9.0 release(2026-09-30)
  4. [4]Open Wearables documentation(2026-09-30)
Supplemental curator note

Open Wearables normalizes data from multiple wearable providers and exposes it through REST APIs, webhooks, and MCP. Because this is sensitive health data, production deployments should explicitly design credential handling, access controls, retention, backups, provider terms, and the scope of data exposed to AI systems.

Try it in 3 steps

  1. 1

    Clone the repository

    Check out the 0.9.0 release tag if you want a version-pinned evaluation.

    git clone https://github.com/the-momentum/open-wearables.git && cd open-wearables
  2. 2

    Create environment files

    Create local backend and frontend configuration and review the default credentials.

    cp ./backend/config/.env.example ./backend/config/.env cp ./frontend/.env.example ./frontend/.env
  3. 3

    Start with Docker Compose

    Launch the developer portal and API, then change the initial admin password after first login.

    docker compose up -d
Check the official README

Growth

Growth trends · Last 30 days

2,586 Stars

Trend data is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • apple-health
  • apple-watch
  • fastapi
  • fitness
  • fitness-analysis
  • fitness-api
  • garmin
  • health
  • healthcare
  • healthcare-ai
  • python
  • quantified-self
Stars
2,586
Forks
497
Watchers
24
Open issues
182
Owner type
Organization
Primary language
Python
License
MIT
Repository last updated
Sep 29, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?