Find the right FatSecret tool/method. Use first if unsure what is available.

Whether YOUR FatSecret account is linked.

Start linking YOUR real fatsecret.com account. Returns an authorize URL — open it, log into (or create) your FatSecret account, and approve. FatSecret then shows you a PIN; pass it to fatsecret_complete_auth to finish.

Finish linking your FatSecret account using the PIN FatSecret displayed after fatsecret_start_auth.

Remove your stored FatSecret tokens from this server.

Search FatSecret's public food database by keyword. Each result's food_description carries per-serving calories and macros; use fatsecret_get_food for structured serving data. NOTE: on the free Basic tier this database is US-only — for Danish foods, look the item up in a Danish food-data source first, then log the closest match here with the serving quantity scaled so the macros line up.

Full nutrition detail + servings for one food by id (from fatsecret_search_foods).

Fuzzy-matches a natural-language quantity ("1 slice", "100g", "medium") against a food's servings, so you don't have to eyeball the raw servings array before logging it.

Search the public recipe database by keyword.

Full ingredients/directions/nutrition for one recipe by id.

Your FatSecret profile status.

Your food diary entries for one date, or a whole month with monthSummary=true.

Dry-run: prepare logging a food into your diary (use fatsecret_pick_serving first to get servingId). Nothing is written until fatsecret_commit_prepared_operation confirms this.

Dry-run: prepare editing an existing food diary entry.

Dry-run: prepare deleting a food diary entry.

Dry-run: prepare copying one day's food entries to another date.

Your weight history for a month containing the given date.

Dry-run: prepare logging your current weight (kg). Height/goal-weight can only ever be set on your very first weigh-in — pass firstTimeSetup=true only then. Cannot backdate more than 2 days.

Your exercise diary entries for one date, or a month summary with monthSummary=true. Also lists known exercise types when includeTypes=true.

Dry-run: prepare an exercise-diary write. FatSecret has no ad-hoc single-workout create — only a recurring weekly template (exercise_entries.save_template), committing that template into a day's diary (exercise_entries.commit_day), and shifting minutes between two exercises on an existing day (exercise_entry.edit). For a one-off workout you'll never repeat, use fatsecret_log_one_off_exercise instead.

Orchestrates a one-off, never-to-repeat workout via FatSecret's template mechanism: saves your CURRENT template (to restore after), overwrites it with a template containing only this workout, commits that into the diary for the given date, then restores your original template. If a step fails partway, this tool attempts a best-effort restore and tells you to check fatsecret_get_exercise_entries / your template state — it cannot guarantee atomicity across FatSecret's three separate API calls. Requires FATSECRET_ENABLE_WRITES.

Your saved-meal templates, or the foods inside one with savedMealId.

Dry-run: create/edit/delete a saved-meal template.

Dry-run: add/edit/remove a food inside a saved meal.

Dry-run: mark/unmark a food or recipe as a favorite. (Adding/removing works on the Basic tier; listing favorites back requires Premier.)

Execute a previously prepared write after the caller has reviewed it. Requires the full operation object back plus a restated confirmOperationHash and a fresh idempotencyKey.

Executes ONLY the profile.create fallback auth path. Requires FATSECRET_ENABLE_PROFILE_CREATE=true. Prefer fatsecret_start_auth/fatsecret_complete_auth for real accounts.

Allowlisted escape hatch for read-only (GET) FatSecret methods not covered by a dedicated tool. Mutating methods are rejected — use the prepare/commit tools instead.