Lifesum alternative
Lifesum doesn't publish one you can connect — so you can't log your Lifesum diary from Claude or ChatGPT. Nutrition MCP does the same job by conversation, and it's free and open source.
The short answer
The Model Context Protocol (MCP) is the open standard that lets AI assistants like Claude and ChatGPT connect to outside tools. Lifesum doesn't publish a public MCP server, so there's no official way to log food to your Lifesum diary from your AI. If you searched for “Lifesum MCP” or “connect Lifesum to Claude,” what you're really after is a nutrition tracker that lives inside your AI — that's exactly what Nutrition MCP is.
What you get instead
Say “oatmeal with banana and peanut butter” and your AI logs calories, macros, fiber, total sugar, caffeine, saturated and trans fat. Generic foods take their values from USDA FoodData Central when it has them, and estimates cover the rest; each number is tagged with where it came from. Log a meal ingredient by ingredient, or save the meals you eat often and log them again by name.
Send a product barcode and pull the label macros from Open Food Facts — fiber and sugar too, where the label lists them. Free for everyone, with no subscription.
Log body weight in kg or lb, and tape measurements of nine body sites in cm or in, set calorie, macro, saturated fat, fiber, sugar, caffeine, and water goals — fiber a target to reach, saturated fat, sugar and caffeine limits to stay under — and track trends toward a goal weight. Alcohol tracking is there too, opt-in and off unless you turn it on.
Ask for daily totals, weekly trends, streaks, and recurring meal patterns — right in the chat.
Import your meal history from another app's CSV export — parsed in your browser, not by the AI. Take everything back out whenever you want: one ZIP with your meals, saved meals, water, weight, body measurements, goals and profile, plus your account record, usage telemetry and connected apps, as CSV files. Meals are the only part that can be imported back in for now. Or delete your account, just as easily.
MIT-licensed and self-hostable — no ads, no paywall, no upsell. Audit the code or run your own instance.
Lifesum vs. Nutrition MCP
Lifesum pairs tracking with structured diet plans. Nutrition MCP is a leaner, free way to log calories, macros, and weight by talking to your AI.
Also compared: MyFitnessPal vs. Nutrition MCP · Cronometer vs. Nutrition MCP · Lose It! vs. Nutrition MCP · MacroFactor vs. Nutrition MCP · Yazio vs. Nutrition MCP
Moving from Lifesum
Lifesum leans on structure and feedback — diet plans, recipes, and its food-rating system that scores what you eat. Nutrition MCP doesn't grade your foods with a badge, so if that scoring loop is what motivates you, Lifesum has an edge there.
The trade is flexibility: rather than a fixed rating, you can ask your AI “is this a good choice for my goals?” and get a real answer in context. Logging is a single sentence, trends and a target weight come built in, and there's no premium tier gating the useful parts.
A badge tells you a food scored 3 out of 5; a conversation can explain why, in the context of your own log — “swap half the rice for greens and this fits your day.” And because Lifesum puts diet plans and some tracking behind Premium, Nutrition MCP is the free option of the two.
Your Lifesum history
Ask to import and an importer opens right in the chat: pick your export, map the columns, preview what will be added, then confirm. The file is read in your browser — the AI never sees the rows. In clients without in-chat panels, paste your export instead.
Moving trackers means moving your history, and you don't have to retype a line of it. Ask to import and an importer panel opens in the chat: you pick your Lifesum CSV export, it's parsed in your browser, and you point its columns at date, food, meal, calories, protein, carbs, fat, fiber, total sugar, and caffeine. Lifesum's headings aren't recognised by name the way MyFitnessPal's, Cronometer's, Lose It!'s, and MacroFactor's are, so that mapping is a one-time manual step — after it you preview what will be added and confirm.
Nothing hides behind an assumption. The mapper shows you your own file — its real headings, real cells, and a running count of the rows that will be created — so a column aimed at the wrong field is visible before anything is written rather than discovered afterwards. Quoted fields, line breaks inside a cell, blank-ish values, and totals rows are all handled, and because the file is read in your browser the AI never sees a row it could mistype.
European exports are covered: a semicolon-delimited file with comma decimals reads correctly, DD/MM/YYYY dates convert once you've confirmed the order, and kilojoules become kilocalories with the unit shown next to a worked example from your own first row. Localised headings help too — a German export's Kalorien, Kohlenhydrate, Ballaststoffe or Koffein fills itself in, and fiber, sugar and caffeine are matched in Spanish, French, Italian and Dutch as well — so the manual mapping is usually shorter than it sounds. Run the import twice and nothing doubles — each row carries a content fingerprint, so repeats are reported as already logged, as long as your timezone hasn't changed in between.
How to switch
Works with any MCP client that supports OAuth 2.0 with PKCE. On first connect you create an account with Google or an email and password.
Using ChatGPT or another client instead? The full install guide covers ChatGPT, Cursor, VS Code, Claude Code, and more.
FAQ
Not an official one. Lifesum doesn't publish a public Model Context Protocol (MCP) server, so there's no official way to log to your Lifesum diary from Claude, ChatGPT, or other MCP clients. Some unofficial, community-built servers exist; they aren't made or supported by Lifesum. Nutrition MCP is different: a free, open-source tracker built as an MCP server from the ground up, with its own account, that can import your Lifesum CSV export.
There is no official Lifesum connector for Claude, because Lifesum publishes no public MCP server. One option is Nutrition MCP, a free MCP server listed in the Claude directory: open it at https://claude.ai/directory/nutrition-mcp, click Connect, sign in, and start logging by conversation.
No — there's no badge or numeric score. Instead you can ask your AI “is this a good choice for my goals?” and get a contextual answer that explains the trade-offs, rather than a fixed rating on the food itself.
Yes. Nutrition MCP is completely free and open source, with no premium tier — whereas Lifesum puts diet plans and some tracking features behind a Premium subscription. You need an AI app that supports MCP, such as Claude or ChatGPT, and a free Nutrition MCP account, which you create with Google or an email and password the first time you connect.
If you want to track calories, macros — fiber, total sugar, caffeine, saturated and trans fat included — water, and weight without opening a separate app or tapping through a food diary, yes. You describe what you ate in plain language, send a photo, or scan a barcode, and your AI logs it. Generic foods take USDA FoodData Central values when it has them, packaged products come from Open Food Facts by barcode, and estimates cover the rest — completely free and open source.
Yes, using manual column mapping. Ask to import and an importer opens in the chat: you pick your Lifesum CSV export, it's parsed in your browser rather than read by the AI, and you point its columns at date, food, meal, calories, and macros — fiber, total sugar and caffeine included — yourself. Lifesum isn't one of the four exports recognised by column name, so that mapping is a one-time manual step, though headings the mapper already knows fill themselves in. Semicolon-delimited European files with comma decimals, DD/MM/YYYY dates, and kilojoules are all handled, and re-importing the same file creates no duplicates as long as your timezone hasn't changed in between. In clients without in-chat panels you can paste your export instead.
Not when the importer opens. It parses the CSV in your browser and shows you what will be added before anything is written: how many meals, the calorie total, anything it had to flag, and the rows themselves — a long file lists the first of them plus a count of the rest rather than every line. Only the rows you confirm are sent, and they go as structured data rather than through the AI's reply, so no row can be mistyped or invented in transit. Each row also carries a content fingerprint, so running the same file again reports those meals as already logged instead of duplicating them, as long as your timezone hasn't changed in between. If your client can't display in-chat panels, the fallback is to paste the export — the AI does read it on that path, so prefer the importer when you have the choice.
Yes. Nutrition MCP is completely free with no premium tier, ads, or paywalled features — unlike apps that put some features behind a subscription. You need an AI app that supports MCP, such as Claude or ChatGPT, and a free Nutrition MCP account, which you create with Google or an email and password the first time you connect.
Free and open source — no Lifesum account, no app to open.
Lifesum is a trademark of its respective owner. Nutrition MCP is an independent, open-source project and is not affiliated with, endorsed by, or sponsored by Lifesum. Comparisons reflect publicly available information at the time of writing and may change.