Blog · How to track calories

How do you log calories in Claude?

Connect IZeat using the supported path for Claude, verify that the account check identifies your own account, then describe a meal and inspect the saved receipt. IZeat provides the persistent record; client eligibility, remote HTTP support, sign-in and tool permission are prerequisites, and a successful account read alone does not prove that a meal was written correctly.

What do you need before you start?

For the complete recording routine, use how to track calories: identify the food and portion, keep its nutrition source visible, then check the daily total.

IZeat is the five-star chef calorie tracker that suggests satisfying, great-tasting meals, so you enjoy every calorie you have left. It works inside ChatGPT, Claude or any other assistant: IZeat knows your numbers for the day, which foods fill you up and what you like. For Claude, use an IZeat account and a client with compatible remote HTTP MCP, browser sign-in and permission to call the tool. A local stdio-only configuration is not equivalent.

Read the provider’s current guidance and IZeat’s connection guide before following a remembered menu path. Provider access and any assistant subscription are separate from IZeat. This editorial review checked documentation on October 3, 2026; it did not test a live connection on every account or device.

How do you connect IZeat to Claude?

From the connection guide, where a button opens Claude with the name and the address already filled in; you review them and confirm. A manual path exists too, and the same page carries it, along with the one for the iPhone app. The steps are not reprinted here on purpose: menus move, and one copy kept current beats two copies drifting apart.

What does not move is the shape of it. The sign-in is IZeat's own page rather than a Claude setting: it is where you say which IZeat account this Claude may write to, and the same Assistants page revokes it whenever you want. Nothing is installed on your machine either, because IZeat is a remote server Claude calls over HTTP.

How do you check it works before trusting it with a meal?

Ask "Who am I in IZeat?" before the first operation. Expand the client’s connector or tool activity and inspect the actual result returned by IZeat’s account-read tool, not just the assistant’s answer. Check that the successful result identifies your authorised IZeat account and email, and the date in its known time zone. If the client does not expose that result, a plausible account name in chat is not proof; use the maintained client guide to check the connection before writing.

“Who am I in IZeat?”

Only use the account you authorised. If the actual result identifies another account, stop and revoke that connection from the Assistants page. If the result reports a missing time zone, giving your city is a separate profile change. A missing name or target does not block a meal. The "IZeat ·" prefix is a display convention that a model can copy or omit; it does not prove the origin or success of a call.

What do you say for the first meal, and what comes back?

Name the meal, the foods, and how much of each. A weight in grams or a volume in millilitres is best; a brand helps; say what a dish was cooked in. Claude is asked to follow IZeat's protocol: to ask what your words leave open, if anything, then to call IZeat once with the whole meal. Here is a real one, from Laetitia, who builds IZeat with Seb, on the morning of Saturday 5 September 2026, dictated to the Claude iPhone app in French and translated here from her export.

She said: "I want to record a breakfast, and it is in fact Saturday 5 September, 7:14 in the morning. So I am going to eat a kiwi, a fresh one, and a galette; look at the photo for the macros." The photo was the galette's nutrition label. Claude read the label, called IZeat once with both items, and answered from the receipt: breakfast recorded for Saturday 5 September, 256 kcal, 13 g of protein, 28 g of carbohydrate, 10 g of fat, with 1494 kcal and 107 g of protein left against her target. It then added, in its own voice, that this galette was the plain one, not the brown one from the day before, with half the fibre, and that 13 g of protein was light for her day. That remark is Claude reasoning over IZeat's figures; the figures are IZeat's. The words “going to eat” describe an intention, not confirmed consumption. This historical recording is therefore not the workflow to copy: ask for a calculation without saving, then record the meal only after confirming what you actually ate. The transcript does not establish that the kiwi had been eaten when breakfast was stored.

Two minutes later she mentioned a protein bar bought for later. Claude asked for its label or its brand, because bars range widely, and offered to wait. She answered: "I would rather you wait until I have eaten it; I will tell you when." Claude wrote nothing. At 7:32 she sent the bar's label, and the second receipt came back: 217 kcal, 20 g of protein, 16 g of carbohydrate, 8 g of fat, source label, and the day so far at 473 kcal. Sending a label alone also does not confirm consumption. For this workflow, explicitly confirm the bar was eaten before recording it; the later receipt does not by itself establish that missing fact.

Read the receipt, not the chat around it. It begins with "IZeat ·", lists each food with its quantity in grams, the meal's calories and macros, then the day's total and, once you have set a target, what is left. Each row keeps its own source: the galette and the bar came from their labels; a food you name without a label is valued from a reference table for the grams you gave, and a dish nobody can look up is an estimate, marked as such. Ask "what is in my breakfast?" or open the web app to see the source row by row. If a figure is wrong, say the right one, and the row is updated with the day.

What you sayWhat Claude is asked to doWhat the receipt shows
"Breakfast: two eggs, 40 g of oats, 200 ml of whole milk"Value the three from reference tables and record themThree rows: oats and milk as reference values for the amounts you gave, the eggs at an assumed weight per egg that the receipt states, the meal total, the day so far
A photo of the yoghurt's label, "I had 125 g"Read the label back with its units, then recordOne row, source label, scaled to 125 g
"Lunch was chicken and rice"Ask the weights, whether the rice is cooked weight, and the cooking fat, in one messageNothing until you answer; then the rows with their sources
"Same breakfast as yesterday, without the milk"Read yesterday's breakfast from IZeat and record today's with the changeThe rows recorded today, the day so far
"The rice was 200 g, not 150"Update the row through IZeatThe change and the new total; the previous state kept in the meal's history
"What is left for dinner?"Read the day from IZeat and answer from itA signed read: the day's meals, the total and what is left, nothing written
Six things to say to Claude once IZeat is connected, and what each one returns; the receipts and the day's figures are IZeat's, only the advice around them is Claude's.

Bottom line: a sentence with weights is recorded as said; a sentence without them costs one question; a question about the day writes nothing, but its figures are still signed by IZeat.

For your first write, inspect the actual IZeat tool result: it must confirm the meal was recorded, with the intended date, foods and quantities. Then open that day in your IZeat web diary and compare the saved meal and its sources. A fresh tool read is useful too, but two matching chat answers are not persistence evidence. If the result is an error or confirmation is pending, check the saved day before retrying; do not assume nothing was written. This verifies the particular operation you checked, not every future call.

What do you do when it goes wrong?

Connected to Claude, IZeat is designed to make the diary easier to keep while you work toward your goal; when something is off, the receipt is what tells you, and these are the cases the connection guide records.

  • A missing "IZeat ·" prefix. The prefix is a display convention, not proof of provenance. Inspect the actual connector/tool result and check the saved meal in the web diary; wording alone does not settle whether a call worked.
  • "Requires sign-in" was turned on. Claude then asks for a client id and a secret nobody has. Turn the switch off, or start the form again with it off: the name and the address are the whole form, and IZeat brings its own sign-in page when Claude hands you over.
  • A second lunch is refused. There is one meal of each type per day; "for lunch I also had a yoghurt" adds to the lunch, and something eaten at another time goes under another meal type. The refusal is signed and ends with "Nothing was recorded".
  • The date is wrong. Say the day in words, "yesterday", "Tuesday"; IZeat resolves it in your time zone and names it in every reply. If the time zone is wrong, say your city and it is stored.
  • A photo of a plate got a number without a question. That is not the protocol; say the portion and the cooking fat and ask for the item to be corrected, and the row is updated with its source.
  • A signed reply says the IZeat tools changed. Claude keeps the list of tools it loaded when the connector was added. If a meal comes back with a reply saying the tools changed and nothing was recorded, remove the IZeat connector and add it again once. A line starting with "New:" is a different thing: a capability announced once, with nothing to fix.

What this page will not settle: the menus, which move, and which the connection guide carries instead. And the record is only as good as the sentence: a weight said fixes the amount, not where the figure comes from, which the receipt says item by item; a weight left open is a question or an estimate that says so.

Frequently asked questions

Short answers to the questions people type, each one sourced above.

Can Claude track calories on its own, without IZeat?

The assistant can calculate a described meal and maintain a list in a conversation; memory features may also retain some context. None of those proves that an external diary was updated, or that a new chat will retrieve a complete, accurate day. With a compatible authorised IZeat connection, inspect actual tool results and the saved web diary rather than relying on remembered chat totals.

Does this work in the Claude iPhone app?

Eligibility and controls depend on the particular client, version, account and workspace policy. Check the official guidance and the maintained connection guide; this review does not certify an untested device or provider.

What does the button on the Assistants page do?

It opens claude.ai in your browser with the connector's name and the address already filled in, so you review them and confirm instead of pasting; it is the same connector the manual path creates. We have not tested it from the desktop app or from a phone: there, the manual steps above are the ones to follow. Once confirmed, Claude brings you to IZeat's sign-in page; sign in, tap Allow, and ask the check question.

Is my IZeat data safe with Claude connected?

Claude can read and write your IZeat record only through the connection you authorised, for the account you signed into, and you can revoke it from your Assistants page at any time. IZeat's server receives only the tool request Claude sends, such as a meal to record, and returns only the account data needed to answer it; what you say to Claude itself is governed by Anthropic's own policy. The privacy page has the detail.

Do I have to set a target to log a meal?

No. A missing name or target never blocks a meal; the receipt then shows the meal and the day's total without a remainder. When you want a target, say it: "from Monday, 1 900 kcal and 130 g of protein". IZeat records it from that day, and every receipt after that ends with what is left. IZeat calculates no target for you; Claude can reason about one with you, outside IZeat, and IZeat stores what you choose.

Can I log by voice in Claude?

If you dictate the meal into Claude's text field, yes: it is recorded the same way as typed text, with the same questions when a weight or a fat is left open; whether Claude's voice mode can use a connector is not something we have tested. What matters is that the words carry the grams; "a big bowl of pasta" said aloud is still a portion nobody weighed, and it is recorded as an estimate marked as one.

How do I fix a mistake Claude made in my diary?

Say the right figure: "the rice was 200 g, not 150", "it was almond milk, not cow's milk". The row is updated through IZeat, the day is summed again, and the previous state stays in the meal's history. Undo shows what the last change did and asks before taking it back, within 48 hours. Every write returns a result you can inspect for a mistake; detection is not guaranteed.

Does the same setup work in ChatGPT or Claude Code?

Follow the separate guides for ChatGPT, Claude and Claude Code. Each client has its own transport, authorisation, account and workspace controls; a working connection in one does not configure another.

The diary you don't type.

Start my 7-day free trialHow it works

Say what you ate to the assistant you already use, ChatGPT, Claude or any other. It is logged, every number says where it came from, and the whole day is on one screen. 7 days without a card.