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.

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.

Back to Delx Wellness

OpenClaw profile pack

Delx Wellness for OpenClaw

Delx Wellness for OpenClaw turns OpenClaw into a recovery-aware wellness agent. It installs a dedicated delx-wellness profile under ~/.openclaw-delx-wellness, writes OpenClaw-native mcp.servers presets for wearable and nutrition MCPs, adds SOUL.md, AGENTS.md, onboarding and wellness skills, and validates setup without creating a hosted token vault.

OpenClaw-nativeLocal-firstmcp.serversskills.load.extraDirsDoctor checks

Start the setup Repository

Private local workspace for an OpenClaw wellness agent

A runtime-native OpenClaw profile, not a fork.

Config, workspace, skills and connector presets stay on your machine.

OpenClaw config

Writes ~/.openclaw-delx-wellness/openclaw.json using the real mcp.servers and skills.load.extraDirs schema.

Workspace ready

Creates a dedicated workspace with SOUL.md, AGENTS.md, ONBOARDING.md and wellness-profile.json.

Doctor checks

Validates OpenClaw config, lists MCP servers and can run an optional chat readiness check.

Public-safe

Contains templates, skills and presets only. Tokens and private health exports stay in local connector setup.

Install the whole stack

One command wires WHOOP, Garmin, Oura, Strava, Fitbit, Google Health, Withings, Apple Health, Samsung Health, Polar and Nourish into a single OpenClaw profile.

terminal

npx -y delx-wellness-openclaw setup
openclaw --profile delx-wellness agent --local --message "Open Delx Wellness onboarding"

Verify before you trust it

MCP checks do not require model quota. The final chat check is opt-in because it sends a short OpenClaw agent turn.

verify.sh

npx -y delx-wellness-openclaw doctor --profile delx-wellness --run-openclaw
openclaw --profile delx-wellness mcp list
openclaw --profile delx-wellness mcp show nourish --json
openclaw --profile delx-wellness models
npx -y delx-wellness-openclaw doctor --profile delx-wellness --run-openclaw --test-chat

Commands

delx-wellness-openclaw setup
delx-wellness-openclaw install
delx-wellness-openclaw onboarding
delx-wellness-openclaw doctor
OpenClaw profile model setup
OpenClaw skills.load.extraDirs
OpenClaw mcp.servers presets

Installed files

SOUL.md
AGENTS.md
ONBOARDING.md
workspace/.openclaw/delx-wellness.json
skills/delx-wellness-onboarding/SKILL.md
skills/delx-wellness-training/SKILL.md
skills/delx-wellness-nutrition/SKILL.md

Privacy

The package contains templates, skills and connector presets only.
It does not contain user tokens, OAuth credentials, chat-channel secrets or hosted hub API keys.
Hosted hub mode requires an explicit --hub-url and never defaults to the public marketing site.
The onboarding worksheet is local to the OpenClaw profile workspace.