Blog · How to track calories

How do you log calories with a compatible MCP client?

Connect IZeat using the supported path for a compatible MCP client, 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 a compatible MCP client, 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 add IZeat to a client that reads a list of servers?

Use the address and the client-specific configuration in the connection guide, then complete the browser sign-in. File schemas differ between clients; there is no universal JSON block. Consult the client’s own instructions for transport and authorisation, and verify your account before sending a write request.

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 in any assistant: 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.”

IZeat sends the model its instructions when the client connects, and a model that follows them asks what the words leave open, then calls IZeat once with the whole meal, each item with its grams, calories, macros and source.

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 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: here the chicken and the potato are reference values for the grams you gave and the sauce is an estimate, which is why the meal is marked estimated; ask "what is in my lunch?" or open the web app to see the source row by row.

What IZeat's instructions ask of the modelWhat the client has to allow, as we reason itWhat you see if it works
Ask one bundled question when the amount, the serving of a homemade dish or the cooking fat is left openShow the model's question before any tool call, without a prefixA question, then a receipt; never a number from a bare photo
Call IZeat once with the whole meal, each item with its sourcePass the tool call and its result through as returnedOne receipt per meal, beginning with "IZeat ·", with the total and what is left
Keep the "IZeat ·" prefix on every answer built on an IZeat result, reads includedNot rewrite or strip the tool resultA read of the day signed the same way as a write
Relay a refusal as returned; it says "Nothing was recorded" and what to do nextNot paper over an errorA signed refusal, and nothing written
Read a meal back before correcting it, then update itLet the model read, then write, in the same turnThe change and the new total, the previous state kept
Five things IZeat's instructions ask of the model that reads your sentence, and what a client must allow for them to happen; the second column is our reading of what a client must allow, not a tested list, and instructions guide the model without guaranteeing it.

Inspect the actual tool result and saved diary to verify the operation; text formatting alone cannot establish client compatibility.

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 any client, 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 that differ from the named assistants.

  • The client asks for credentials. IZeat uses its own browser sign-in and authorisation for the account you choose. Configure remote HTTP and authentication using the client-specific connection guide and that client’s official documentation. There is no universal rule to leave credential fields empty: if the client requires unsupported credentials or cannot complete the sign-in flow, stop rather than guessing settings.
  • The client asks for a command to launch. IZeat is remote; there is no command. Look for the remote, http or url option in the client's server settings, and use the address alone.
  • 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 photo of a plate got a number without a question. That is not the protocol; the model did not follow the instructions it was given, or the client did not pass them. Say the portion and the cooking fat and ask for the item to be corrected.
  • The model ignores IZeat and answers from memory. Some clients may keep a server's tools off until you enable them for the session, or need the model to be told; say "record this in IZeat" and look for the receipt. If it never appears, the client's own documentation says how its tools are enabled.

The limit, plainly: IZeat has tested the assistants its docs name and makes no claim about any other client or model, whether Gemini, Mistral, a local model or a tool of your own; the check question and the receipt are how you find out, and the sentence is only as good as the weights it carries.

Frequently asked questions

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

Does IZeat work with Gemini, Mistral or a local model?

This requires a client with compatible remote HTTP MCP, browser sign-in and permission to use IZeat’s tools, plus eligible account and workspace access. Use the connection guide for your client; this does not establish compatibility with every assistant. The MCP authorisation specification describes the protocol; consult your client’s own documentation for implementation and access controls. This review has not certified those clients.

What is MCP, in plain words?

MCP, the Model Context Protocol, is an open standard that lets an assistant use outside tools during a conversation: a server publishes what it can do, the assistant calls it with what you said, and the server answers with facts. IZeat is such a server: it can record a meal, read a day, set a target. The assistant supplies the model that understands your sentence; IZeat supplies the record, the calculations and the instructions that ask the model to question before it estimates.

Is there a token or an API key to paste?

IZeat uses its own browser sign-in and authorisation for the account you choose. Configure remote HTTP and authentication using the client-specific connection guide and that client’s official documentation. There is no universal rule to leave credential fields empty: if the client requires unsupported credentials or cannot complete the sign-in flow, stop rather than guessing settings.

Can several clients use the same IZeat account?

Yes: each is a connection to the same account, listed in the connection guide, and each can be revoked on its own. A meal recorded from one client is in the day another reads, with the same sources and totals, because IZeat holds one record. The web app shows that record on any device, read-only.

What if my client shows the tool result raw?

Then you are reading the receipt itself, which is the point: the result carries a statement that begins with "IZeat ·" and states what was recorded, the meal total and what is left, next to the same figures as data. A client that shows it raw is relaying it as returned. What matters is that the model's own words around it do not replace it, and that provenance is checked against the actual tool result, regardless of prefix.

Does IZeat send the client anything besides tool results?

Its instructions, once, when the client connects: what the tools do, what to ask before estimating, how to sign a reply, and that the target is the customer's. A model that reads them follows IZeat's protocol; a client that drops them leaves the model to guess, which is one reason a bare photo can come back with a number. Every tool result then carries a statement that begins with "IZeat ·" and the same figures as data, so the receipt you read is what was written.

Is the JSON block the same for every client?

No. Configuration files and schemas belong to the client implementation; there is no universal JSON block. Use that client’s official documentation and IZeat’s connection guide. The MCP authorisation specification describes the protocol, not a particular client’s configuration.

Does the same setup work in ChatGPT, Claude 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.