Summary

check_auth_status is named as the first call for a reason: most of this needs a profile, and part of it needs a Premier tier as well.

The diary, saved meals, favourites, weight and exercise tools all state that they require profile auth, and the vendor puts check_auth_status in front of them to report what is set up before anything fails. A separate line runs through the food side, where find_food_by_barcode, autocomplete_foods, get_food_categories, get_food_sub_categories, get_brands and create_food are each marked Premier exclusive. Two constraints inside the diary are worth knowing before writing against it: edit_food_entry cannot change an entry's date, and edit_saved_meal_item cannot change its serving_id.

What it is

A FatSecret client with 44 tools covering the food and recipe database, a user's food diary, saved meals and favourites, weight and exercise logging, and the credential and OAuth setup every profile tool depends on.

What you get

Food lookup: search_foods across the database, get_food for servings, calories, macros and micronutrients, find_food_by_barcode for GTIN-13 with UPC-A, EAN-13 and EAN-8 support, and autocomplete_foods for a partial expression.
Recipes: search_recipes filtered by calories, carb, fat and protein percentages, prep time and recipe types, get_recipe for ingredients, directions and nutrition, and get_recipe_types.
Catalogue reads: get_food_categories, get_food_sub_categories and get_brands filtered by starting letter and brand type.
The food diary: get_food_entries by date or entry id, get_food_entries_month for a per-day calorie and macro summary, create_food_entry, edit_food_entry, delete_food_entry, copy_food_entries between dates and copy_saved_meal_entries into a meal.
Saved meals and favourites: create_saved_meal, edit_saved_meal, delete_saved_meal and get_saved_meal_items with add, edit and delete for its items, plus get_favorite_foods, delete_favorite_food, get_favorite_recipes, add_favorite_recipe, delete_favorite_recipe, get_most_eaten_foods and get_recently_eaten_foods.
Weight and exercise: update_weight, where the first weigh-in also requires goal_weight_kg and current_height_cm, get_weight_month, get_exercises, edit_exercise_entries for shifting minutes between activities, get_exercise_entries_month, and save_exercise_template for chosen days of the week.
create_food for a custom food with its full nutrition panel, and get_profile for the authenticated user's profile status.
Setup as tools: check_auth_status for what is configured, setup_credentials to store API credentials, and start_auth with complete_auth for the OAuth 1.0 flow that grants profile access.

Requirements

FatSecret API credentials stored through setup_credentials, and — for anything touching a user's diary — an authorised profile from the OAuth 1.0 flow in start_auth and complete_auth. find_food_by_barcode, autocomplete_foods, get_food_categories, get_food_sub_categories, get_brands and create_food are marked Premier exclusive.

Setup effort

One command plus a key — npx fatsecret-mcp, then supply credentials