Reference guide · updated August 11, 2026
Choose the provider you already trust, confirm the records your workflow needs, and keep authorization outside the model context. There is no universal “best” wearable connector — there is a connector that fits the data, privacy and client you actually use.
Short answer
Start with the provider or export already in your life. Then check three things: what data is available, how the connector is authorized, and whether the default behavior is read-only. Open the provider page only after those three checks line up.
These are not ranked winners. They are concrete paths through the Delx Wellness library, grouped by the data source an agent already needs: recovery, sleep, body composition, local exports, endurance training and device-specific APIs.
OAuth 2.0
WHOOP MCP server for recovery score, HRV, sleep stages and day strain.
Best fit: Best for recovery-led athletes, coaches and personal agents that need a WHOOP MCP connector for daily readiness, sleep and load briefings before training.
OAuth 2.0
Oura MCP server for readiness, sleep, HRV, activity and SpO2.
Best fit: Best for sleep-first agents and coaches that need an Oura MCP connector for readiness, overnight recovery and daily activity context.
OAuth 2.0 signed
Withings MCP server for smart-scale composition, sleep stages and heart records.
Best fit: Best for body-composition, sleep and cardiometabolic wellness agents that need a local Withings MCP connector for smart-scale and device records.
OAuth 2.0
Fitbit MCP server for activity, sleep stages, intraday heart and HRV data.
Best fit: Best for broad wellness agents that need a Fitbit MCP connector combining activity, sleep, HRV, breathing, weight and food/water logs.
Local CSV/ZIP export
Samsung Health MCP server for local CSV/ZIP exports from Galaxy Watch and Android.
Best fit: Best for Galaxy Watch users who want a local Samsung Health MCP connector in an agent without handing over a Samsung account or waiting for an Android bridge.
Local export.zip
Reads your local Apple Health export with no live HealthKit dependency.
Best fit: Best for users who want Apple Health context in an agent without relying on a live API, cloud sync or background mobile service.
Google OAuth 2.0
Google Health API v4 beta connector for Fitbit, Pixel Watch and unified health data.
Best fit: Best for builders migrating Fitbit integrations, Pixel Watch users, and early Google Health API testers who want an agent-ready local OAuth workflow.
OAuth 2.0
Strava MCP server for runs, rides, swims, segments and activity streams.
Best fit: Best for endurance agents and coaches that need a Strava MCP connector for route-aware activity details without exposing GPS by default.
Local Garmin Connect
Body Battery, training readiness, sleep, HRV and stress.
Best fit: Best for endurance athletes and daily agents that need a broad view of sleep, stress, Body Battery, training readiness and recent activities.
OAuth 2.0
Nightly Recharge, training load, PPI/HRV and continuous samples.
Best fit: Best for training agents that need Polar recovery, sleep, continuous samples, route-aware sessions and test results.
Mobile-app password grant
Eight Sleep MCP server for nightly scores, temperature schedules, alarms and base state.
Best fit: Best for sleep-focused agents that need an Eight Sleep MCP connector for pod temperature, alarms and nightly score without copy-pasting from the app.
A different data shape
Nourish is the Delx Wellness nutrition layer. It is a local-first MCP server for calories, macros, TACO/BR food search, barcode image decoding, meal photo previews, carbon context and nutrition trends, built to sit beside wearable connectors instead of pretending to be another device provider. It can read public food sources and write a local log, so its default workflow is preview, confirm, then log — never a silent mutation. Use it beside any connector when an agent needs food, hydration or goal context.
Read the Nourish MCP install and limits01
A sleep-focused agent needs different records from a body-composition review or an endurance training loop. Read Data Availability before installing.
02
OAuth, local exports and mobile-app credentials have different trade-offs. Prefer the path you can revoke, inspect and keep on the machine you control.
03
Run setup, auth and doctor. Start with connection_status, privacy_audit and a daily or weekly summary before fetching detailed records.
Keep provider tokens and exports outside the model context. Ask for bounded summaries first, request raw payloads or location only with permission, and treat the result as wellness context, not diagnosis. Eight Sleep write tools, where available, are explicitly opt-in; the other connector pages document their own conditional and unavailable records.
There is no universal best connector. Start with the provider or export you already use, then choose the connector whose data availability, authorization path and privacy model match the agent workflow you want.
Yes. Delx Wellness connectors expose standard MCP configuration for Claude Desktop, Cursor, ChatGPT Desktop, Hermes, OpenClaw and other compatible clients. Each provider page includes the exact setup and doctor commands.
The Delx Wellness local-first connectors keep provider credentials on the machine running the connector. The agent receives bounded MCP responses, not the OAuth secret. Hosted Cloud is a separate opt-in path with its own security and account model.
No. These connectors expose wellness context such as sleep, activity, recovery and body records. They are not diagnosis, treatment, emergency monitoring or a replacement for a clinician.
No. Nourish is the separate Delx Wellness nutrition MCP module: it handles food lookup, barcode and meal-photo previews, local intake, hydration, goals and nutrition summaries. It is local-first, write-capable only after explicit confirmation, and does not provide clinical guidance.