Wellness Nourish
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FDC_API_KEY | No | USDA FoodData Central API key (optional, for higher rate limits) | |
| NOURISH_MCP_PORT | No | Port for Streamable HTTP server (default: 3000) | |
| NOURISH_LOCAL_DIR | No | Path to local data directory (default: ~/.wellness-nourish) | |
| NOURISH_FIXTURE_DIR | No | Directory containing fixture data (default: fixtures) | |
| NOURISH_OFF_ENABLED | No | Set to '1' to enable Open Food Facts barcode and product search | |
| NOURISH_FIXTURE_MODE | No | Set to '1' to use fixture data instead of real API calls |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nourish_agent_manifestA | Return agent-facing install, safety, resource, and first-call guidance. |
| nourish_capabilitiesA | Describe supported nutrition workflows, providers, and recommended first tools. |
| nourish_connection_statusA | Report local storage, fixture, USDA, and Open Food Facts readiness without returning secrets. |
| nourish_quickstartA | Personalized 3-step setup walkthrough for the human user. Adapts to current state (USDA key set? OFF enabled? local-dir writable?). Call this first when the user asks 'how do I use this?' |
| nourish_demoA | Returns realistic example payloads of nourish_search_food, nourish_estimate_meal, and nourish_daily_summary so agents see the contract before any real call. |
| nourish_privacy_auditA | Describe local storage, secret handling, source licensing, and safety boundaries. |
| nourish_profile_getA | Returns the shared Delx Wellness profile (~/.delx-wellness/profile.json). Read-only. Surfaces calorie/macro targets, dietary preferences, restrictions/allergies, and goals so nourish coach/suggest tools can personalize meals. |
| nourish_profile_updateA | Persist a partial patch to the shared Delx Wellness profile. Requires explicit_user_intent: true. Rejects any field containing oauth/token/secret/password/cookie/refresh/api_key/session — the profile is for non-secret wellness context only. |
| nourish_onboardingA | Returns the 11-question onboarding flow for the shared Delx Wellness profile. Read-only. The agent should ask these questions next so wellness-nourish (and the rest of the wellness stack) can personalize responses — non-secret data only, stored at ~/.delx-wellness/profile.json. |
| nourish_search_foodA | Search food providers by query. Use taco or br_local for Brazilian staples, open_food_facts for packaged products, usda for generic foods, or all. |
| nourish_lookup_barcodeA | Lookup a packaged food barcode in Open Food Facts. |
| nourish_decode_barcode_imageA | Decode a barcode from an image path, base64 image, or data URI without logging intake. |
| nourish_lookup_barcode_imageA | Decode a packaged-food barcode image, then lookup the product in Open Food Facts. |
| nourish_get_foodB | Fetch a USDA food by source_id, an Open Food Facts food by barcode source_id, or a TACO food by source_id. |
| nourish_estimate_mealA | Estimate nutrition for a short meal text using local deterministic defaults. Accepts text or meal_text; preserve unresolved and confidence. |
| nourish_estimate_meal_photoA | Estimate meal nutrition from an agent-provided photo observation; always requires user confirmation before logging. |
| nourish_analyze_food_imageA | Route agent-provided food image observations across barcode, nutrition label OCR, or meal-photo estimation without logging. |
| nourish_log_intakeA | Log an intake entry only after explicit user intent. Pass explicit_user_intent: true after the user asks to save/log/register; accepts text or meal_text plus structured food data. |
| nourish_daily_coachA | Summarize today, goal gaps, wearable context, and a safe next action for Telegram-style coaching. |
| nourish_suggest_next_mealB | Suggest a next meal from today's intake, goals, personal memory, and optional wearable context. |
| nourish_after_log_reviewC | Review the day after a meal log and explain what changed plus the next correction or action. |
| nourish_pre_workout_nutritionA | Suggest light pre-workout nutrition using goals, current intake, and optional WHOOP/Garmin context. |
| nourish_evening_checkinC | Check late-day protein, calories, and hydration gaps with a compact Telegram-friendly next step. |
| nourish_pull_wearable_contextA | Read the most recent shared wellness_context (delx-wellness-context/v1) written by a wearable connector to ~/.delx-wellness/, so coach tools can be recovery/strain-aware without the agent passing it inline. Read-only; never fabricates wearable data. If no connector has persisted a context yet, returns available:false with the expected path. The returned context can be passed straight into nourish_daily_coach / nourish_suggest_next_meal / nourish_pre_workout_nutrition as wearable_context (or set auto_wearable:true on those tools to pull it automatically). |
| nourish_remember_mealA | Save a personal meal shortcut locally after explicit user intent, for example 'meu cafe normal' -> '2 ovos e banana'. |
| nourish_list_memoryA | Read local remembered meals and nutrition preferences for personal Telegram shortcuts. |
| nourish_forget_memoryA | Delete a local remembered meal by id or label after explicit user intent. |
| nourish_update_intakeA | Update a local intake entry by id. Quantity or grams_estimate changes rescale nutrients to keep summaries consistent. Gated: requires explicit user intent — agents must not call this autonomously. |
| nourish_list_intakeA | List local intake entries with optional filters: date OR since/until range, meal_type, tag, source_trace, min_confidence, limit. All filters AND together. Returns most-recent-first. |
| nourish_delete_intakeA | Delete a local intake entry by id. Gated: requires explicit user intent — agents must not call this autonomously. |
| nourish_clear_dayA | Delete all local intake entries for a date after explicit user intent. |
| nourish_delete_waterA | Delete a single local hydration entry by id after explicit user intent. |
| nourish_clear_hydration_dayA | Delete all local hydration entries for a date after explicit user intent. Does not touch intake — pair with nourish_clear_day or use nourish_clear_day { include_hydration: true } for both. |
| nourish_carbon_summaryA | Estimate the carbon footprint (kg CO2-equivalent) of a meal, plus optional lower-carbon swap suggestions. Pass |
| nourish_undo_lastA | Undo the most recently logged intake or hydration entry. The most common Telegram/agent recovery move ('I logged the wrong thing'). Returns what was undone so the agent can confirm. Requires explicit_user_intent. Pass kind: 'intake' | 'hydration' | 'any' (default 'any') to scope the undo. |
| nourish_log_waterA | Log local hydration in milliliters after explicit user intent. Pass explicit_user_intent: true after the user asks to save/log water. |
| nourish_hydration_summaryB | Summarize local hydration for a date. |
| nourish_get_goalsA | Read local calorie, macro, and hydration goals. |
| nourish_set_goalsA | Set local calorie, macro, and hydration goals after explicit user intent. Use daily: {...} or flat shortcuts like calories_kcal/protein_g; pass explicit_user_intent: true after confirmation. |
| nourish_goal_progressA | Compute per-day progress vs configured goals (kcal, protein, carbs, fat, water) for today / yesterday / last_7_days / last_30_days. Returns per-day breakdown (consumed, goal, pct, delta_to_goal), period totals, multi-day averages, days_on_target count, and locale-aware next-action recommendations (pt-BR if profile language is Portuguese, otherwise en). Read-only: no logging side effects, no explicit_user_intent required. |
| nourish_daily_summaryA | Summarize local intake totals, confidence, and source coverage for a date. Pass |
| nourish_compare_daysA | Compute a per-nutrient diff between two days' summaries. Returns deltas (date_b - date_a) for calories, protein, carbs, fat, fiber, sugar, sodium plus what changed by meal type. Useful for 'how was today vs yesterday?' coaching. |
| nourish_bulk_log_intakeA | Log multiple intake entries in a single call. Requires explicit user intent (explicit_user_intent: true). Each item is processed through the same text-estimator pipeline as |
| nourish_weekly_summaryA | Summarize seven days of local intake totals from a start date. |
| nourish_export_dataA | Export local intake data as JSONL or CSV without provider secrets or tokens. Defaults to the 500 most-recent rows; pass since/until to scope by date or max_rows to widen/narrow. Omitted rows are reported so you can refine instead of dumping months of history into chat (use the |
| nourish_chatgpt_dashboardA | Open an interactive ChatGPT/MCP Apps dashboard for today's nutrition summary, safe meal estimation, and next-meal coaching. Read-only; logging still requires explicit user confirmation through existing tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| nourish_daily_review | Review a day of logged nutrition while preserving confidence and source coverage. |
| nourish_telegram_meal_log | Handle a Telegram meal message with preview-before-write safety. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| nourish-dashboard | Interactive Nourish dashboard for ChatGPT and MCP Apps hosts. |
| nourish-agent-manifest | Agent-facing install, safety, tool, and resource manifest. |
| nourish-capabilities | Supported nutrition providers and workflows. |
| nourish-privacy-audit | Local storage, secret handling, safety, and source license boundaries. |
| nourish-usage-guide | Agent and human workflows for safe previews, writes, edits, hydration, goals, and exports. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/wellness-nourish'
If you have feedback or need assistance with the MCP directory API, please join our Discord server