Blog · How to track calories

How do you log calories in Claude Code?

Connect IZeat using the supported path for Claude Code, 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 Code, 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 Code?

With one command in your terminal, then a sign-in. The maintained command is on the connection guide, with a copy button, and it is not reprinted here: it has changed once already, and a second copy in an article is how a reader ends up running last month's version.

The transport is HTTP because IZeat is remote: there is no command to launch and nothing on your machine to keep running. The sign-in is IZeat's own page. Claude Code opens it in your browser, or prints the address for you to open when it has no browser to reach, and you say there which IZeat account this Claude Code may write to.

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?

The same sentence as anywhere else: the meal, the foods, how much of each, a weight in grams or a volume in millilitres when you have it, and what a dish was cooked in. For example:

“For lunch I had 180 g of grilled chicken breast, no oil, 80 g of steamed sweet potato and about 40 g of my homemade sauce.”

Claude Code receives IZeat's instructions with the connection: ask what your words leave open, if anything, then call IZeat once with the whole meal. The receipt is what tells you it did.

IZeat · Recorded for Friday 11 September 2026 (today): lunch — grilled chicken breast 180 g, steamed sweet potato 80 g, homemade sauce 40 g — 455 kcal · P 58g · C 20g · F 15g (estimated). Total: 455 kcal · P 58g · C 20g · F 15g. Against the target: 1545 kcal remaining · 92g protein remaining.

Read the receipt, not the output around it: it begins with "IZeat ·", and it is the same receipt in every assistant; the Claude guide walks through it row by row. In a terminal it arrives as text among your other output, which is what the prefix is meant to help with: it is there as a visual cue on IZeat's own lines. Meant to, and no further, because keeping it is asked of the model rather than enforced: a figure that lost it can still be the record's, and a figure carrying it can still be the model's.

What you sayWhat Claude Code is asked to doWhat the receipt shows
"Who am I in IZeat?", in a sessionCall IZeat's account check and relay the answerAn answer naming your account, your email and today's date in your time zone; nothing written
"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
"Lunch: 180 g of grilled chicken breast, no oil, 150 g of cooked rice, a 125 g plain yoghurt", typed between two commitsValue the three from reference tables and record themThree rows, source reference, the meal total, 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
"Undo that"Show what the last change did and ask before taking it backThe change previewed, signed, ending with "Nothing was changed yet"; nothing taken back until you confirm
"What is left for dinner?", at the end of the working dayRead 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 Code 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 Code's.

Bottom line: the terminal changes nothing about the record; a sentence with weights is recorded as said, and a question about the day writes nothing.

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 Code, 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.

  • The command ran but nothing asked you to sign in. Type /mcp in a session. Anthropic's documentation describes it as the panel that lists the servers and lets you sign in to one; we have not re-tested it. Then ask the check question.
  • 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.
  • 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 signed reply says the IZeat tools changed. Claude Code keeps the list of tools it loaded when the server was added. If a meal comes back with a reply saying the tools changed and nothing was recorded, run claude mcp remove izeat, then the add command again once; Anthropic's documentation says removal also forgets the sign-in, so expect to sign in again. A line starting with "New:" is a different thing: a capability announced once, with nothing to fix.

The limit, plainly: the record is only as good as the sentence. A weight said fixes the amount, not where the figure comes from: a label, a reference table or an estimate, and the receipt says which. A weight left open is a question, or an estimate that says so. Use the actual IZeat tool result to establish the origin of a figure; a missing prefix is inconclusive.

Frequently asked questions

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

Is IZeat a local MCP server or a remote one?

Remote, over HTTP, with its own sign-in: the command adds it with the http transport, and nothing runs on your machine. There is no stdio server to install, no token to paste and no process to keep alive; Claude Code opens IZeat's sign-in page when it needs it, and the connection is tied to the IZeat account you sign into. You can revoke it from your Assistants page at any time.

Does the terminal change how a meal is recorded?

No. The record and the protocol are IZeat's, whichever assistant you talk to: the same sentence, the same bundled question when a weight or a fat is left open, the same returned receipt with the meal total and what is left. What changes is where you type it; a meal said in Claude Code shows on the web app and reads back in Claude or ChatGPT the same way, because it is one record.

Can I use the same IZeat account from Claude Code and from Claude?

Yes: each assistant is a connection to the same account, listed in the connection guide, and each can be revoked on its own. A meal recorded from the terminal at lunch is in the day that Claude on your phone reads in the evening, with the same sources and totals, because IZeat holds one record and the assistants read and write it through their own connection.

Where is my day shown, if I never open a screen?

On the web app, read-only, in a browser: the day as a list with a total, every meal with its numbers and sources, the target and what is left, the week and the history. In the session you can also ask what is left, or what a meal contained, and the answer is a signed read from IZeat. Neither asks you to type a meal into a form.

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 Code can reason about one with you, outside IZeat, and IZeat stores what you choose.

How do I fix a mistake made in my diary from the terminal?

Say the right figure: "the rice was 200 g, not 150". The row is updated through IZeat, the day is summed again, and the previous state stays in the meal's history. "Undo that" shows what the last change did, changes nothing, and asks; you confirm within ten minutes, and only a change made in the last 48 hours can be undone. Restore works the same way, in two steps, for something undone in the last 48 hours. Every write returns a result you can inspect for a mistake; detection is not guaranteed.

What does the check question prove?

A successful actual IZeat account-read result verifies access to the account it identifies for that call. The assistant naming an account or showing the IZeat prefix is insufficient. It does not prove that a meal was written: inspect the write result and check the saved day in the web diary.

Does the same setup work in ChatGPT or Claude?

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.