ChatGPT Plugin

Food Tracker

Log meals and see what's left

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Food Tracker is a personal nutrition log you keep by talking to ChatGPT. Send a photo of your plate, a voice note or a sentence like "two idlis and sambar for breakfast"; ChatGPT works out each item's portion, calories, protein, carbs, fat, fibre and key vitamins and minerals, shows you the list, and records it once you agree. Ask "how much protein is left today?" or "how did I do this week?" and it reads your log back. It also keeps your weight and body-composition readings (including photos of smart-scale printouts), steps and workouts, your meal plan and your daily and per-meal targets, which it can suggest from your goal and pace. Everything is also visible at foodtracker.in. For adults who want to track what they eat without typing into an app. Figures are estimates, not medical advice. You need a Food Tracker account; you sign in and approve access when you connect.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-17
Tool count: 15
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Food Tracker has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

15 tools agents can invoke

Remove an entry by id.
delete_food_entry
Totals, targets, remaining, calorie split, weight and activity for a day. Default: today.
get_daily_summary
Entries for one date, or a range up to 31 days. Entries include ids for update/delete.
get_food_log
Per-day calorie and macro totals for a range (default last 7 days), including days with no entries, plus averages over logged days.
get_nutrition_trend
Food Tracker server 1.4.2. Timezone, meal plan (which meals the user eats, labels and time windows), body profile, estimated daily energy burn (BMR/TDEE), goal, targets and latest weight and body composition. Call once per session; its reply also states the server version.
get_profile
Daily calorie and macro targets in effect on a date (default today).
get_targets
Weight and body-composition entries for a date range (default last 30 days) with 7-day moving averages for weight, muscle and body fat.
get_weight_log
Record steps, active/workout calories, workout minutes or water for a date (default today). Only passed fields change.
log_activity
Record one or more food items for a meal. Pass every item of the meal in one call. Returns the created entries and the day's running totals versus targets.
log_food
Record body weight for a date (default today), with body composition when known: body fat %, skeletal muscle mass, fat mass, body water, and tape measurements. Values may be read from a smart-scale or body-composition (InBody/BCA) printout photo. One row per date: logging the same date again overwrites weight; a composition field that is omitted keeps its stored value, null clears it.
log_weight
The user's meal plan: up to 12 meals plus the fixed catch-all 'other'. Each meal has a stable key, a label and an optional time window. Pass a preset (two_meals: lunch+dinner; three_meals; three_meals_two_snacks), or 'slots' as the whole plan in the order wanted: a slot without 'meal' creates a new meal (its key is derived from the label, e.g. 'Post-dinner snack' → post_dinner_snack); a known key or label updates that meal (omitted fields keep their values); meals not listed are turned off, not deleted. Use 'remove' to delete meals for good: their logged food moves to other. Renaming keeps the key and the entries.
set_meal_plan
Set calorie and macro targets per meal from a date onward (default today), for the meals in the user's plan. Pass explicit values per meal, or use_suggested: true to split the current daily target by how much each meal usually carries; explicit values override suggested ones. Explicit values patch the targets in effect: meals not mentioned keep theirs, and null clears a value. Or scale_to_daily: true to keep the current meal proportions and re-fit them to the daily target in effect. Meal targets are independent of the daily target and need not add up to it.
set_meal_targets
Set daily calorie and macro targets from a date onward (default today). Earlier days keep their old targets. Pass explicit values, or use_suggested: true to take the goal-based suggestion from get_profile / update_profile; explicit values override suggested ones.
set_targets
Correct any field of an existing entry by id. Only the fields passed are changed.
update_food_entry
Change the goal (lose / maintain / gain), goal weight, body details, training schedule or timezone. Only the fields passed change. Returns the new energy estimate and goal-based suggested targets; targets themselves are not changed, so confirm with the user and call set_targets to apply them.
update_profile

FAQs

Food Tracker ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Food Tracker's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.