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

Security and trust

Local-first trust, hosted convenience.

Name: Delx Wellness for OpenClaw
Brand: Delx Wellness

Delx Wellness keeps the open-source connector layer useful on your machine. The paid cloud layer adds OAuth hosting, remote MCP, encrypted persistence, audit and operational support.

View hosted MCP docs Request beta access

Encrypted token vault

Hosted provider token sets are encrypted before storage. The public open-source connectors still keep local tokens on your own machine or server.

Hashed API keys

Wellness Cloud API keys are shown once. The hub verifies keys from salted hashes and tracks usage without storing plaintext secrets.

Export and delete

Export/delete controls are intentionally outside the paid-tool gate so a user can retrieve or remove stored hub data even if billing lapses.

Hardened staging

The hosted hub runs behind Caddy on loopback, with systemd sandboxing, unprivileged service user, scoped env file permissions and Postgres migrations.

Product boundary

Useful wellness context without medical overreach.

The product is designed for personal planning, agent context, habit reflection and recovery-aware workflows. It should not be positioned as clinical software.

Delx Wellness is wellness context for planning and reflection, not diagnosis, treatment, emergency monitoring or medical advice.

Provider integrations are unofficial unless a provider explicitly says otherwise.

Raw provider payloads, sensitive details and location-like data stay opt-in where a connector exposes them.

Coach workflows will require explicit client consent before any client data sharing is exposed.

Production state

The beta has real infrastructure, with a few known gates before public self-serve.

Hosted hub

Private beta staging is live at api.delx.ai/wellness-hub with API key authentication and plan gates.

Database

The hub uses Postgres migrations for users, API keys, OAuth connections, usage, audit and billing entitlement state.

Billing gates

Premium MCP tools require an active Wellness Cloud plan; export/delete and privacy audit remain accessible.

Stripe

Founding access is captured now; live checkout depends on completing the Stripe account/legal setup.