delx-living-body

Meta-MCP that turns 15 wellness MCPs into one unified body data layer for AI agents.

Today, answering "should I train hard today?" forces an agent to orchestrate WHOOP recovery, Garmin Body Battery, Oura sleep, Nourish nutrition, and cycle phase across five separate MCP servers. That's brittle for users and confusing for the agent.

delx-living-body is one MCP server that:

1. Auto-detects which of 15 Delx Wellness connectors you already have installed locally — no manual config
2. Composes parallel calls to the right subset
3. Synthesizes a natural-language answer plus a structured reasoning trace and per-source confidence — using rule-based reasoning, no LLM calls

Install it once. Get a unified body data layer. Works with whatever wellness MCPs you already have.

Install

npx -y delx-living-body

That's the whole install. No OAuth flow, no API keys — delx-living-body has no auth of its own. Each child connector handles its own credentials.

See it answer "What should I do today?" (no accounts needed)

git clone https://github.com/davidmosiah/delx-living-body && cd delx-living-body
npm install && npm run build
npm run demo

The demo boots the real MCP server, fakes three installed connectors (WHOOP + Oura + Garmin, backed by a bundled stub child that carries synthetic body data), and drives it over stdio exactly the way an agent does. No real accounts, API keys, or network. Captured output lives at examples/demo-what-should-i-do-today.txt:

2) living_body_ask  question="What should I do today?"
────────────────────────────────────────────────────────────────
Recommendation:
   Today at a glance: recovery 74, sleep 83, body battery 68.

Confidence: high   Sources: whoop, oura, garmin

3) living_body_ask  question="Should I train hard today?"
────────────────────────────────────────────────────────────────
Recommendation:
   Green light for a hard session. Recovery and sleep both support high intensity.

Confidence: high   Sources: whoop, oura, garmin

Reasoning trace (rule-based, no LLM):
   Intent classified as: training_readiness
   - (rec_high) Recovery 74 supports a high-intensity day.
   - (sleep_good) Sleep score 83 is supporting recovery.

One question in → one synthesized answer composed across all three connectors, with a stable reasoning trace and zero LLM calls. This is the Body-vertical entrypoint: install once, ask in plain language, get a unified answer.

Tools (6)

How detection works

For each known connector, delx-living-body checks:

1. ~/.<vendor>-mcp/tokens.json exists
2. ~/.<vendor>-mcp/config.json exists (password-based connectors like Eight Sleep)
3. An export file at the path in the vendor's env var (Apple Health, Samsung Health)
4. ~/.delx-wellness/profile.json lists the device

If any check passes → detected. Otherwise → missing (with install hint). Stateless connectors (Cycle Coach) are always considered available.

Detection results cache for 60s (DELX_LIVING_BODY_DETECT_TTL).

Known connectors (15)

... View full README on GitHub