Open Wearables Release 0.3 Alpha: Flutter SDK, MCP Server
Key takeaways
- First mobile SDK: Flutter package (health_bg_sync) for Apple Health. Handles background sync, historical backfill, and token-based authentication via iOS Keychain.
- MCP Server connects Open Wearables to Claude and ChatGPT. Query health data in natural language directly from an LLM.
- Redesigned developer dashboard with dedicated views for workouts, activity, sleep, and body measurements.
- Extended Garmin support, XML uploads, Sentry error handling added.
Open Wearables 0.3 alpha is available on GitHub.
Flutter SDK for Apple Health
The health_bg_sync Flutter package handles the full Apple Health integration lifecycle: permission flows, background sync, historical backfill, and incremental data transfer. Authentication uses token-based auth stored in iOS Keychain. Sessions restore automatically on app restart.
Data arrives in Open Wearables in the same normalized format used by Garmin, Polar, and other providers. No separate parsing logic needed on the application side.
Note: this is an alpha. The Apple Health SDK is functional but the onboarding flow and data source prioritization have known rough edges being addressed in the beta.
MCP Server
The MCP Server exposes wearable data as tools for LLMs. Connect it to Claude or ChatGPT and query health metrics in natural language: ask about last week's HRV trend, compare sleep across devices, or list recent workouts. The server translates natural language queries into Open Wearables API calls and returns structured results.
Developer dashboard
Redesigned with dedicated views for workouts, activity, sleep, and body measurements. Improved data visibility across connected providers.
What's next
0.3 beta matures the Apple Health SDK with invitation code onboarding, refresh token support, and adds Strava as a provider.
Want to see it in action? Book a demo
