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

Hosted beta

Delx Wellness Cloud

Hosted OAuth, remote MCP, persistent nutrition and wellness memory, API keys, audit controls and setup help for users who do not want to operate the local stack.

Open source stays freeRemote MCPOAuth vaultNourish CloudCoach-ready

Request beta access View pricing Setup docs

Wearable data sources connected to an AI wellness layer

Local-first trust, hosted convenience.

The paid layer sells hosting, identity, persistence and support. The open-source connectors remain useful.

Hosted OAuth

Connect supported providers once, then use a scoped remote MCP endpoint instead of managing refresh tokens across machines.

Persistent memory

Keep nutrition, hydration, goals and normalized wellness summaries available to ChatGPT, Hermes, OpenClaw and custom agents.

Audit and privacy

API keys, provider status, audit events, export/delete controls and conservative wellness claims stay visible from the dashboard.

Recovery loops

Turn readiness, sleep, training load and nutrition context into safe agent prompts for daily planning and workout adjustment.

Commercial shape

The open-source layer gets people in. The hosted layer removes operational drag.

Users can still run everything locally. Cloud is for the moment they want continuity across devices, ChatGPT, agents, teams and coach workflows without becoming their own auth and data operator.

Free layer

Connectors, docs, local Nourish and profile packs remain open-source.

Paid layer

OAuth, token refresh, remote MCP, persistence, API keys, audit logs and setup help.

Expansion

Coach dashboards, consented client reports and recovery-to-workout loops once individual usage is stable.

Production guardrails

Built for sensitive wellness context, not medical claims.

The beta is for planning, reflection and agent context. It is not diagnosis, treatment, emergency monitoring or a replacement for professional care.

Provider tokens encrypted in the hosted vault.

API keys verified from hashes, not stored as plaintext.

Export/delete controls are part of the product surface.

Raw payloads and sensitive details stay opt-in.

Audit events are visible before coach/team expansion.

Provider limitations and unofficial status stay explicit.

Read security model

Beta path

Start with Nourish, then expand into hosted recovery context.

Phase 1

Nourish Cloud: persistent nutrition, hydration, goals, export/delete and ChatGPT-ready MCP.

Phase 2

Wellness Hub Pro: hosted OAuth, remote MCP, provider status, API keys and normalized daily context.

Phase 3

Coach workflows: client consent, weekly readiness reports and recovery-to-workout recommendations.

Founding beta

Join with setup help while the hosted product is still high-touch.

Best fit: users already trying the open-source connectors, AI-agent builders, quantified-self users and coaches who want an early hosted wellness context layer.