Wellness Nourish: local nutrition search and logging (no OAuth needed)

Who it is for

If you want to look up food, look up barcodes, log a meal, or log water on your own computer without OAuth, Wellness Nourish matches that kind of local nutrition task. Official docs call it a “local-first” nutrition service: food search, barcode lookup, intake logging, and water, and they say it can work without OAuth. A harder boundary: tokens do not leave your machine.

It is for people ready to run one official install command in a terminal and immediately do one low-risk search, not people who only want to browse a product definition. Official docs also say you can attach this connector alone to Claude Desktop, Cursor, or ChatGPT Desktop. Those are wiring targets, not a second main install path. When you attach it alone, still finish the official install below first, then confirm the connector appears in that client.

If you need barcode parameters, intake fields, a water-write interface, or an undo method that official docs have not written, the current description does not get you there. Do not treat that as a ready-to-follow procedure. Local-first only means tokens stay on this machine. It does not automatically mean no local reads or writes, and it does not mean the install never touches the network.

First try in 3 minutes

Use only this official install path.

Prerequisites: this machine can run npx. You do not need to apply for OAuth. Official docs say tokens do not leave this machine. Also remember: install changes local config, and the offline demo still calls a published package.

Install and config location: run this official command in a terminal. Official docs say it prewrites this connector and the full Delx Wellness stack into a dedicated config file.

npx -y delx-wellness-hermes setup

The first call must name the official search tool. Do not do intake or water writes first. Run this offline fixture command. The tool is search, the query is banana, and keep the offline switch:

NOURISH_FIXTURE_MODE=1 npx -y wellness-nourish search banana

Keep the offline switch. The fixture ships with the published package and is resolved from the package root. Success has two layers: the install command finishes and writes the dedicated config file; then this food search completes and the offline fixture demo works. Official docs do not give a returned-field inventory. Confirming that a search happened is enough. If the command fails or there is no search output, stop here. Do not switch to logging a meal or water.

Use cases

Case 1: first confirm food search runs on this machine. The only official call that writes both a tool name and parameters is the search banana command above with the offline switch. The purpose is to confirm the published wellness-nourish package can find its bundled fixture and finish one food search. Stop when you observe a search result for banana. Official docs do not say which nutrition fields come back. Do not invent those details, and do not read this step as already logging a meal.

Case 2: barcode lookup, or estimating a Brazilian meal. Official docs put barcode lookup, intake logging, and water in the same capability sentence. 0.7.0 also writes TACO 4 meal estimates for Portuguese Brazilian foods, with examples cafezinho, feijão, concha, and churrasco-style meals. Both needs match written capabilities, but official docs give no barcode tool name, no meal-estimate tool name, and no parameter table. Today you can only tell that the page claims these capabilities, not how to call them or what they write. Intake logging and water are clearly writes. Do not run them until you see officially named tools in the client. Official docs also give no undo or rollback path, so do not call writes reversible.

Limits

Local-first and no OAuth. Tokens do not leave this machine. Do not infer from that: no network, no local reads, or no privacy boundary. The install command changes a dedicated config file. The offline demo still calls a published package through npx. Even if the first try is search-only, this machine still runs an external package and may read fixture files bundled in the package.

The official one-click install preconfigures this connector and the full Delx Wellness stack. This page does not expand any second install command, so competing install styles are not written as parallel main paths.

The offline demo depends on in-package fixtures and must keep the officially written offline switch. TACO 4 only covers the officially named Brazilian Portuguese food scenes. Do not extend it to an unpublished ingredient library. Barcode, intake, and water are capability names only, with no call format. You can attach it alone to Claude Desktop, Cursor, or ChatGPT Desktop, but wiring details follow each client’s own config UI. That official sentence does not give a config snippet.

Docs page: https://github.com/davidmosiah/wellness-nourish