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

Pricing

Free local stack. Paid hosted convenience.

Name: Delx Wellness for OpenClaw
Brand: Delx Wellness

Open-source connectors stay free. Hosted plans charge for OAuth, remote MCP, persistence, audit controls, billing, quotas and setup help.

Request access Ask about beta View cloud beta

Wellness planning studio for hosted AI agent workflows

Start small, sell the operational layer.

The founding offer bundles Nourish Cloud and Wellness Hub beta access while the product is still high-touch.

Open Source

For local-first users and builders.

Free

Beta hypothesis

Public MCP connectors
Local Nourish module
Hermes and OpenClaw profile packs
MIT-licensed docs and examples

Run locally

Founding Cloud

High-touch beta while the hosted layer matures.

USD 19/mo

Beta hypothesis

Hosted Nourish Cloud beta
Wellness Hub Pro beta access
Setup help
Remote MCP and API key path
Export/delete and audit controls

Request access

Coach Starter

Planned after individual cloud usage is stable.

USD 149/mo

Beta hypothesis

Client consent workflow
Weekly readiness reports
Recovery-to-workout planning
Coach notes and support

Discuss pilot

After founding beta

Split the bundle once usage tells us what people actually pay for.

The first product should be easy to buy and high-touch. After usage is real, split nutrition, hosted wearable context and coach workflows into clearer plans.

Nourish Cloud

USD 9/mo target

Persistent nutrition, hydration, goals, summaries and export/delete.

Wellness Hub Pro

USD 29/mo target

Hosted OAuth, provider status, remote MCP, API keys and normalized daily context.

Developer/API

USD 499+/mo target

Managed wellness context API, quotas, support and custom integration work.

No medical claims

Pricing covers hosted software, support and wellness context. It does not sell diagnosis, treatment or emergency monitoring.

Cloud is optional

The local open-source stack remains useful. Paid plans remove operational work rather than locking basic functionality.

Coach plans later

Coach and team pricing should wait until consent, reports and privacy workflows are proven with individual users.

Founding access

Request founding access without leaving Wellness.

This form writes to the same Nourish Cloud lead pipeline as the billing page. Paid-entitled Nourish accounts can use the account page to generate the remote MCP key; Stripe checkout will replace the pending flow as soon as the live product, price and webhook secrets are installed.

Open Nourish account page