Delx Living Body
Unify multiple installed wellness MCP connectors into one composable body-data layer for agents instead of hand-merging each source per prompt.
Overview
io.github.davidmosiah/delx-living-body is a MCP server for the Build phase that auto-detects wellness connectors and composes them into one cached body-data layer for agents.
What is this MCP server?
- Auto-detects installed wellness connectors and composes a single body data layer
- SQLite response cache with configurable path and disable flag
- Detection cache TTL defaults to 60 seconds (DELX_LIVING_BODY_DETECT_TTL)
- Spawns child connectors via configurable npm runner (default npx)
- npm package delx-living-body v0.2.0 over stdio
- Server version 0.2.0
- Transport: stdio
- Default detection cache TTL: 60 seconds
What problem does it solve?
Each wellness MCP needs separate configuration and prompts, so multi-source body context never stays in sync across agent sessions.
Who is it for?
Builders assembling a personal or product-grade wellness agent stack with several Delx-style or third-party connector MCPs.
Skip if: Single-source exports only, or teams that want one flat REST API with no local child MCP processes.
What do I get? / Deliverables
One meta-MCP discovers child wellness servers, caches responses, and presents unified body data to your agent.
- Unified agent tools spanning detected wellness MCPs
- Cached responses with tunable detection TTL
- Documented child connector spawn behavior via npm runner
Recommended MCP Servers
Journey fit
Meta-MCP composition is build-phase agent infrastructure when your product touches more than one health or wearable connector. It discovers and orchestrates child wellness MCP servers rather than replacing a single vendor integration.
How it compares
Meta-MCP orchestrator, not a replacement for a dedicated Apple Health or wearable connector.
Common Questions / FAQ
Who is delx-living-body for?
Indie developers wiring multiple wellness MCP connectors who want one agent-facing layer for sleep, activity, and related body signals.
When should I use delx-living-body?
Use it after at least one wellness MCP is installed, when you need detection, caching, and composed queries during build and agent-tooling setup.
How do I add delx-living-body to my agent?
Register delx-living-body as a stdio MCP server via npm, set optional cache and detect TTL env vars, ensure child connector packages are installable via your npm runner, then query through the unified tools.