How many wellness MCP connectors does Delx Wellness publish?

Delx Wellness publishes 10 public local-first MCP connectors: WHOOP, Oura, Garmin, Strava, Fitbit, Google Health, Withings, Apple Health, Samsung Health and Polar. Plus the Nourish nutrition module and profile packs for Hermes and OpenClaw.

What does 'agent_ready' mean for a connector?

agent_ready is the highest tier in the Delx Wellness connector quality standard. It guarantees connection_status, daily_summary and weekly_summary tools, an agent_manifest resource, a privacy_audit tool, read-only defaults and provider-tagged structured responses suitable for an AI agent to reason over.

Which MCP clients can install these connectors?

Any MCP-compatible client. The library was tested against Claude Desktop, Cursor, ChatGPT Desktop, Hermes and OpenClaw. The fastest paths are the one-command Delx Wellness for Hermes and Delx Wellness for OpenClaw profile packs.

Can I install all connectors at once?

Yes. The packages are independent and coexist cleanly. The fastest way 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.

Are these connectors official from each device maker?

No. Each connector is unofficial and not affiliated with the device maker. They use public APIs where available. Garmin uses your own Garmin Connect login locally. Apple Health reads a manual export.zip rather than live HealthKit. Samsung Health reads a local personal-data CSV/ZIP export rather than live Health Connect.

Where do my OAuth tokens go?

Tokens stay on your machine in ~/. -mcp/ with chmod 600. They are not uploaded to a hosted hub and the MCP client never receives them. Every connector ships a privacy_audit tool so an agent can verify posture without calling the upstream API.

Connector library

Every wellness connector, one library.

Name: Delx Wellness for OpenClaw
Brand: Delx Wellness

10 local-first wearable and health connectors — same install pattern, same privacy model, same documentation shape. Nourish sits next to them as the nutrition layer.

Skip the per-client wiring