Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer.
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 matrixliving_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.Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| 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. |
claude mcp add delx-living-body --env DELX_LIVING_BODY_CACHE_PATH=your-value --env LIVING_BODY_MCP_HOST=your-value -- npx -y delx-living-body| 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 |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.