Strength + readiness
Train
Recovery, HRV and training load become context before the workout starts.
10 open-source connectors·MIT licensed
The wellness layer
for AI agents.
Open-source MCP connectors for 10 wearable/API/export sources and a local nutrition module — give your AI sleep, recovery, training and food context. Local-first, read-only, tokens stay on your machine.
Works in any MCP client
Claude DesktopCursorWindsurfHermesOpenClawChatGPT DesktopCustom MCP agentsCodexClaude DesktopCursorWindsurfHermesOpenClawChatGPT DesktopCustom MCP agentsCodex
10Connectors
1Nutrition module
MITLicensed
0Hosted vaults
~60sFirst setup
Real-world context
Built for real training days.
This isn't another dashboard. It turns the signals from your wearables into the context an agent needs to help you train, recover and plan your day.
Outdoor cardio
Move
Runs, rides and routes stay provider-tagged for cleaner agent reasoning.
Mobility + sleep
Recover
Your assistant can connect today's plan with yesterday's recovery.
Nutrition layer
Food, hydration and goals — all local.
Wearables explain readiness and recovery. Nourish adds calories, macros, hydration and goals as local agent context. It runs as its own MCP server, sitting beside the wearable connectors so your agent can reason across both.
USDAOpen Food FactsBarcode imagesMeal photosMCP
Food lookup
USDA-first search, Open Food Facts barcode lookup and local barcode image decoding for packaged items.
Meal context
Preview text or photo-assisted meal estimates before writes, preserving confidence and provenance.
Daily tracking
Local intake, hydration, goals, daily summaries, weekly summaries and CSV export.
terminal
npx -y wellness-nourish doctor
npx -y wellness-nourish log --preview "2 eggs and banana"
npx -y wellness-nourish today --format markdownAgent surface
wellness-nourish
Barcode-aware packaged food lookup from digits or images.
Photo meal previews require confirmation before logging.
JSONL and CSV export stay local.
Hydration and goals complete the day view.
How it works
From wearable to AI in three steps.
Each connector is a standalone npm package — local-first by design, read-only by default, privacy modes built in.
01
Install
One npx command per connector. No global install, no Docker, no servers to babysit.
$ npx -y whoop-mcp-unofficial setup
02
Authorize
Browser-based OAuth or a local helper. Tokens land in ~/.<provider>-mcp/ with chmod 600.
$ npx -y whoop-mcp-unofficial auth
03
Ask your agent
Paste the snippet into Claude Desktop or Cursor. Or skip the wiring with one command for Hermes or OpenClaw.
$ Should I train hard today?
Connectors
One catalog. Every wearable.
10 wearable and health connectors — each installable on its own, read-only by default, and tagged agent_ready. Nourish sits beside them as the nutrition layer.
WHOOP
whoop-mcp-unofficial
Recovery score, HRV, sleep stages and day strain.
RecoveryHRVSleepStrainWorkouts
OAuth 2.0
Oura Ring
oura-mcp-unofficialDaily readiness, sleep periods, HRV trend and SpO2.
ReadinessSleepActivityHRVSpO2
OAuth 2.0
Garmin Connect
garmin-mcp-unofficialBody Battery, training readiness, sleep, HRV and stress.
SleepHRVBody BatteryStressTraining Readiness
Local Garmin Connect
Strava
strava-mcp-unofficialRuns, rides, swims, segments and per-second activity streams.
ActivitiesStreamsRoutesAthlete Stats
OAuth 2.0
Fitbit
fitbit-mcp-unofficialActivity, sleep stages, intraday heart and HRV.
ActivitySleepHeart RateHRVSpO2Weight
OAuth 2.0
Google Health
google-health-mcp-unofficialGoogle Health API v4 beta connector for Fitbit, Pixel Watch and unified health data.
Google Health API v4Fitbit MigrationStepsSleepHeartRollups
Google OAuth 2.0
Withings
withings-mcp-unofficial
Smart-scale composition, sleep stages and ECG-grade heart records.
Body MeasuresSleepActivityHeart Records
OAuth 2.0 signed
Apple Health
apple-health-mcp-unofficialReads your local Apple Health export with no live HealthKit dependency.
ActivitySleepHeart RateHRVWorkouts
Local export.zip
Samsung Health
samsung-health-mcp-unofficialReads Samsung Health CSV/ZIP exports for Galaxy Watch wellness context.
Galaxy WatchSleepHeart RateHRVWorkouts
Local CSV/ZIP export
Polar
polar-mcp-unofficial
Nightly Recharge, training load, PPI/HRV and continuous samples.
Nightly RechargeTraining SessionsPPI SamplesSleepContinuous HR
OAuth 2.0
Exercise Catalog
exercise-catalog-mcp-privatePrivate exercise catalog bridge for agent-built workouts.
ExercisesMuscle GroupsEquipmentVideo GuidanceWorkout Builder
Private provider token
PrivateDetails
Quick start
Copy. Paste. Run.
Pick your MCP client, paste the snippet, then run setup for the connectors you actually use. You'll be live in about a minute.
terminal
# Recommended for Hermes — installs the wellness profile,
# all 10 wearable/API/export connectors, Nourish, skills and onboarding.
npx -y delx-wellness-hermes setup
hermes -p delx-wellness
# Verify (no model required)
npx -y delx-wellness-hermes doctor --profile delx-wellness --run-hermesLive demo
See an agent reason in real time.
Pick a scenario and watch your AI call MCP tools, read provider data, and answer with the full picture. Mock data — same shape your agent gets in production.
Claude Desktop
Ready
Delx Wellness for Hermes
The whole stack in one command.
Tired of wiring each connector by hand? Run one npx command and Hermes becomes a recovery-aware wellness agent — onboarding, skills, all ten wearable/API/export connectors and Nourish, preset and ready for daily use through Telegram or terminal.
terminal
npx -y delx-wellness-hermes setup
hermes -p delx-wellnessOne command
Creates the delx-wellness Hermes profile, installs SOUL.md, ONBOARDING.md and AGENTS.md, plus skills and MCP presets.
Recovery-aware
Onboarding asks injuries, training schedule and conservative rules so the agent never recommends max effort blindly.
Doctor split
MCP readiness vs chat readiness, separate. Setup failures become obvious instead of mysterious.
Compatible with: WHOOP · Oura · Garmin · Strava · Fitbit · Google Health · Withings · Apple Health · Samsung Health · Polar · Nourish all preset
Delx Wellness for OpenClaw
The OpenClaw path is first-class now.
Same wellness stack, but using OpenClaw's own profile isolation, workspace, skills and MCP config schema. No generic paste-and-pray manual JSON glue.
terminal
npx -y delx-wellness-openclaw setup
openclaw --profile delx-wellness agent --local --message "Open Delx Wellness onboarding"OpenClaw-native
Writes the real openclaw.json shape: mcp.servers, skills.load.extraDirs and a dedicated workspace.
Local agent flow
Starts with openclaw --profile delx-wellness agent --local, with onboarding already in the workspace.
No hosted vault
OAuth credentials and health exports stay inside each connector's local setup path.
OpenClaw checks: config validate · mcp list · mcp show nourish verified locally
Privacy & security
Your data stays on your machine.
Health data is sensitive — every connector is built to treat it that way. No hosted Delx vault. No shared cloud for tokens. Only the context you ask your agent to use is shared with that client.
Local-first storage
OAuth tokens are saved in ~/.<provider>-mcp/ with chmod 600. Nothing is uploaded to a hub. No third-party vault.
Read-only by design
No upload scopes are requested. The MCP client never receives access or refresh tokens. Tools never echo secrets.
Built-in audit
Every connector ships *_privacy_audit and *_connection_status tools so agents can verify posture without calling the upstream API.
Privacy modes
summary / structured / raw — defaults are conservative. Raw upstream payloads and GPS coordinates are explicit opt-in.
Not medical advice. These connectors expose user-authorized data for personal AI workflows. They are not medical devices and do not provide diagnosis, treatment or emergency monitoring.
FAQ
Common questions.
Everything you need to know before you wire your first connector.
What is MCP?
Model Context Protocol is an open standard for connecting AI assistants to external tools and data. Any MCP-compatible client — Claude Desktop, Cursor, ChatGPT Desktop, Hermes, OpenClaw, custom agents — can use a connector that speaks MCP.
Should I use a one-command profile pack or wire individual connectors?
Use Delx Wellness for Hermes or Delx Wellness for OpenClaw if you want a daily wellness agent with onboarding included and you want all 10 wearable/API/export connectors plus Nourish ready in one command. Wire individual connectors if you only need one or two providers, prefer Claude Desktop / Cursor as your client, or want full control over the install. Both paths use the same underlying MCP packages.
Why local-first instead of a hosted hub?
Health data is sensitive, and hosted hubs concentrate secrets that become attractive targets. Every connector here runs on your machine, stores tokens locally with chmod 600, and keeps them out of the MCP client. Only the context you explicitly ask your agent to use is shared with that client.
Can I install all 10 at once?
Yes — and they coexist cleanly. The fastest path is npx -y delx-wellness-hermes setup or npx -y delx-wellness-openclaw setup, depending on your runtime. For Claude Desktop or Cursor, paste the multi-server JSON snippet from the homepage Quick start. When two providers cover the same signal, each tool returns provider-tagged data so your agent can reconcile them sensibly.
Are these official?
No — every connector is unofficial and not affiliated with the device makers. They use public APIs where available. Garmin uses your own Garmin Connect login locally, Apple Health reads a manual export.zip instead of live HealthKit, Samsung Health reads a local CSV/ZIP personal-data export instead of live Health Connect, and Google Health uses the new Google Health API v4 (beta until end of May 2026) via your own Google Cloud OAuth client.
Is this medical advice?
No. These connectors expose user-authorized data for personal AI workflows. They are not medical devices and do not provide diagnosis, treatment or emergency monitoring. Always consult a qualified professional for medical concerns.
Can I contribute a new provider?
Yes. The connector quality standard documents the bar for registry_ready and agent_ready connectors. Open an issue or PR on the delx-wellness repo with the provider you want to add and the data you'd expose.
Give your AI a body of evidence.
Ten open-source wearable/API/export connectors, Nourish and profile packs for Hermes and OpenClaw. Your agent reasons across sleep, recovery, activity, training and nutrition locally.