Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer.
If you already use Delx, the delx mcp server is the piece that lets your assistant work with it directly. Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
living_body_status — Which connectors are detected? Safe; no subprocess spawningliving_body_ask — Main tool. Spawns detected children in parallel, returns synthesized answer. Requires explicit_user_intent: trueliving_body_daily_brief — Markdown brief built from each connector's daily_summaryliving_body_compose_context — Normalized delx-wellness-context/v1 shape merged across sourcesliving_body_health_check — All 15 known connectors with install hints for missing onesliving_body_capabilities — Self-description + per-connector availability matrixInstallation goes through your MCP client rather than a global install: point it at delx-living-body on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: DELX_LIVING_BODY_CACHE_PATH, LIVING_BODY_MCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Delx's toolset — living_body_status, living_body_ask, living_body_daily_brief and 3 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| living_body_status | Which connectors are detected? Safe; no subprocess spawning. |
| living_body_ask | Main tool. Spawns detected children in parallel, returns synthesized answer. Requires explicit_user_intent: true. |
| living_body_daily_brief | Markdown brief built from each connector's daily_summary. |
| living_body_compose_context | Normalized delx-wellness-context/v1 shape merged across sources. |
| living_body_health_check | All 15 known connectors with install hints for missing ones. |
| living_body_capabilities | Self-description + per-connector availability matrix. |
## Use with Claude Desktop
```json
{
"mcpServers": {
"living-body": {
"command": "npx",
"args": ["-y", "delx-living-body"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DELX_LIVING_BODY_CACHE_PATH | Filesystem location the server is allowed to use. | Optional |
| LIVING_BODY_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.