diet.chat
Get early access

MCP server

Log your meals from the assistant you already have open

diet.chat exposes its tools over the Model Context Protocol, so Claude — or any other client that speaks MCP — can write to your log and ask questions of it, under access you grant per client and can revoke in one click.

Get early access See how it works

Why this matters for a food log specifically

Friction is the entire ballgame here. A food diary fails at the moment opening it costs more than the entry is worth, and "open another app" is a surprisingly large amount of cost when you're holding a plate.

If you already have an assistant open all day, the lowest-friction food log available to you is the one that lives inside it. Say what you ate in the window you're already typing in; it lands in the same record the web app reads, with the same structure and the same permissions.

The reverse matters too. Your log is one of the more interesting personal datasets you'll ever own, and being able to reason about it in the same conversation as everything else — your calendar, your training, whatever else you've connected — is worth more than any feature we could ship on a screen.

What it isn't

  • Not a copy of your data sitting in someone else's product
  • Not blanket access — tokens are scoped and per client
  • Not permanent. Revoke a client and it stops, immediately
  • Not a different feature set. Same tools, same rules, same log

In practice

The same tools, called from somewhere else

Nothing is special-cased for MCP. The client picks from the same registry the web app uses, and the answers are counted from the same record.

From Claude Chat

Log lunch for me — chicken salad and a coffee, about half twelve — and tell me whether I've been eating lunch at all this month.

Called 3 tools

  • diet_chat.log_meal(items: ["chicken salad", "coffee"], at: "12:30")
  • diet_chat.get_history(meal: "lunch", window: "30d")
  • diet_chat.compare_periods(metric: "evening_eating", group_by: "lunch")

Logged. Lunch has happened on 19 of the last 30 days. On the 11 days it didn't, you logged unplanned evening eating on eight — against three of the 19 days you did eat it.

Called from a different client, against the same log, under a token scoped to your account and revocable from your settings.

Exposed over MCP

log_meal log_photo log_snack log_hunger log_context log_weight get_history find_pattern compare_periods get_trend export_range

Read and write tools are granted separately, so a client can be given the ability to log without the ability to read six months of your eating back out.

Access

How the permissions work

One token per client

Each connected assistant gets its own token. You can see which clients are connected, when each last called something, and what it called.

Scoped, not blanket

Write-only, read-only, or both — chosen per client. A logging shortcut doesn't need to be able to read your history.

Revocable immediately

Revoking a token stops that client mid-conversation. No support ticket, no waiting period, no partial state left behind.

Every call is in the audit log

What was called, when, and by which client. It's your food log — you should be able to see exactly what touched it.

Export is a tool too

Ask your assistant for the last three months as a file and it comes back as one. Portability isn't a premium feature here.

Any MCP client

Claude is what most people will use and nothing is built specifically for it. If your client speaks the protocol, it works.

Questions

What people ask about this

Do I need to use an AI assistant to use diet.chat?

No. The web app is the product and it stands on its own. MCP is for people who already have an assistant open all day and would rather log there.

Does connecting a client send my whole log somewhere?

No. The client calls tools and gets back the specific answers to what it asked — the same as the web app does. Nothing is bulk-copied anywhere, and you can see every call that was made.

Is my log used to train a model?

No. Messages you send are processed by a model provider to produce a reply, under terms that don't allow training on them. Your log isn't sold and isn't training data. The privacy page has the specifics.

Which clients work?

Any that implement MCP. Claude is where most people will start, and we'll test against whatever the waitlist tells us they're actually using — which is exactly why that question is on the signup form.

Early access

Tell us which assistant you use

It's the single most useful thing we can know before launch: the server has to work with whatever you've already got, and this decides which client gets tested against first.

  • Founding accounts lock their price for life
  • MCP is included in the personal plan
  • Export everything you've logged, photos included, whenever you want

No card required. Unsubscribe any time.

Your food log, in the window you're already typing in

Founding pricing is locked for accounts opened during early access.

Get early access See how it works

Founding accounts lock their price for life. No card required.