Wellness MCP Server

Local-first cycle coach MCP for phase-aware nutrition and training context. The wellness mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 13 defined tools rather than through you.

What it actually does

Pass in period start dates (from any source — Apple Health Cycle, Garmin women's health, Fitbit female health, or direct user input) and get back the user's current phase plus phase-aware recommendations for nutrition, training, and hydration. Stateless — the MCP itself never persists cycle data. Supports PCOS-aware mode via the cycle_irregular flag (v0.3.3) — accepts cycles 21-90 days, caps confidence at 'low', and returns a luteal_extended placeholder when standard 14-day-luteal math no longer applies.

Its toolset

Everything the assistant can do here goes through one of these:

• cycle_agent_manifest — Runtime contract
• cycle_capabilities — Phases, upstream connectors, metrics
• cycle_connection_status — Health + stateless reminder
• cycle_privacy_audit — What's logged (nothing) vs sent out (nothing)
• cycle_data_inventory — Phase taxonomy + metric catalog
• cycle_predict_next_period — Average cycle length + next-period date
• cycle_phase_guidance — Recommendations for any specific phase
• cycle_irregular_check — PCOS / irregular-cycle screening from history
• cycle_quickstart — Minimal getting-started walkthrough
• cycle_profile_get — Read the shared Delx Wellness profile (read-only)
• cycle_profile_update — Persist opt-in profile prefs (requires explicit user intent)
• cycle_onboarding — 11-question onboarding flow for the shared profile

Adding it to your client

The server ships on npm as delx-wellness-hermes, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

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. Wellness's toolset — cycle_agent_manifest, cycle_capabilities, cycle_connection_status and 10 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.

This entry was verified against Wellness's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wellness.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wellness mcp server does with a few real requests.