Nutrition module
Nourish MCP
Nourish is the Delx Wellness nutrition layer. It is a local-first MCP server for calories, macros, barcode image decoding, meal photo previews, food provenance and nutrition context, built to sit beside wearable connectors instead of pretending to be another device provider.
{
"mcpServers": {
"nourish": {
"command": "npx",
"args": ["-y", "wellness-nourish"],
"env": {
"FDC_API_KEY": "${FDC_API_KEY}",
"NOURISH_OFF_ENABLED": "1"
}
}
}
}Food data
Search USDA FoodData Central and keep provider attribution in the output.
Barcode lookup
Decode barcode images locally, then use Open Food Facts for packaged foods with license metadata preserved.
Goals
Preview text or photo-assisted meals, then compare calories, macros and hydration against local goals.
Local-first
Food logs stay local and mutating tools require explicit user intent.
Agent workflow
Preview, confirm, log, summarize.
Nourish is write-capable, so the agent contract is stricter than the wearable connectors. Agents inspect status, estimate conservatively, show confidence and only mutate after explicit user intent.
Preview a meal estimate before writing to the local log.
Install Hermes personal mode for Telegram with setup --client hermes.
Search USDA FoodData Central before estimating generic foods.
Lookup packaged foods through Open Food Facts with ODbL attribution.
Decode barcode photos from image paths, base64 images or data URIs before Open Food Facts lookup.
Use agent vision observations for meal photo previews, then confirm portions before logging.
Summarize calories, macros, hydration and goals in agent-friendly markdown.
Export local intake data as JSONL or CSV.
Hermes + Telegram
Personal nutrition tracking from chat.
The Hermes setup writes a dedicated MCP server block, pins the package version and installs a Nourish skill so Telegram flows default to preview, confirmation and local logging, including barcode photos and meal photo estimates.
- Use one local store per personal Telegram profile.
- Agents prefer direct MCP tools instead of shell workarounds.
- Meal messages are previewed before write unless save intent is explicit.
- Barcode photos and meal photos use MCP preview tools before any local log write.
npx -y wellness-nourish setup --client hermes --profile personal --local-dir /root/.hermes/nourish/personal
npx -y wellness-nourish doctor --client hermes --json
hermes mcp test nourishMCP tools
- nourish_connection_status
- nourish_search_food
- nourish_lookup_barcode
- nourish_decode_barcode_image
- nourish_lookup_barcode_image
- nourish_estimate_meal
- nourish_estimate_meal_photo
- nourish_log_intake
- nourish_daily_summary
- nourish_weekly_summary
- nourish_log_water
- nourish_set_goals
- nourish_export_data
Resources
- nourish://agent-manifest
- nourish://capabilities
- nourish://privacy-audit
- nourish://usage-guide
Privacy
- Food logs, hydration and goals stay under ~/.wellness-nourish unless NOURISH_LOCAL_DIR is set.
- No hosted account is required.
- Agents must preserve source attribution, confidence and safety warnings.
- Mutating MCP tools require explicit user intent.
Known limits
- Nutrition estimates are approximate.
- Meal photo estimates depend on the agent vision layer and always require user confirmation before logging.
- No hosted sync or clinical guidance.
- Open Food Facts data carries attribution and share-alike obligations.