Skip to content

Log with AI

Say it once. It’s in your log.

metabomap ships an MCP server, so the AI assistant you already pay for can work your account directly - 42 tools across your diary, blood readings, fasting, training, supplements, recipes and meal plans. Describe the meal; it finds the foods, does the arithmetic, and writes the entry. No copying numbers between apps, no key to paste.

Claude Codex 42 tools Free to connect Revoke in one click

Setup

One URL, then sign in.

It’s a remote connector, so there is nothing to install and no key to copy. You paste one address, sign in to metabomap, and pick what the assistant is allowed to touch.

Connector URL

app.metabomap.com/mcp

The same address in every client. Leave any token or header field blank - signing in is the whole handshake.

Claude

Paste a URL

claude.ai, Claude Desktop, Claude Code

  1. 1 Customize → Connectors → Add custom connector
  2. 2 Paste app.metabomap.com/mcp and choose Add
  3. 3 Connect, sign in to metabomap, and approve what it may touch

Switch it on in a chat from the + menu and start talking.

Codex

Paste a URL

the Codex app and CLI

  1. 1 Settings → Plugins → MCPs → Connect to a custom MCP
  2. 2 Choose Streamable HTTP and enter app.metabomap.com/mcp - leave the token field empty
  3. 3 Save, then Authenticate and approve what it may touch

Or from the CLI:

codex mcp add metabomap --url https://app.metabomap.com/mcp codex mcp login metabomap

Any other client that speaks remote MCP works the same way - there is nothing metabomap-specific in the handshake.

What it can do

42 tools. Every one of them yours to grant or refuse.

These are the real tools the server exposes, grouped by what they’re for. Each family rides its own read and write permission, so a connection can be as narrow as you like - one that drafts recipes but never touches your diary, or one that reads your weight trend but can’t log a weight.

Your food diary

9 tools

Log a meal you describe, a quick freeform entry, one of your recipes, or water - then read the day back with totals and what’s left against your goals.

log_food log_quick_entry log_recipe log_water get_daily_log recent_foods update_diary_entry delete_diary_entry get_micronutrient_report

Includes editing and deleting entries - your assistant can fix a mistake, not just add to it. The micronutrient report is Premium.

Foods and recipes

6 tools

Search the catalog, pull one food’s full numbers, add a custom food off a label, and build multi-ingredient recipes with per-serving nutrition computed for you.

search_foods get_food create_custom_food create_recipe list_my_recipes get_recipe

Glucose, ketones, and the rest

5 tools

Record a reading, or a paired glucose and ketone reading that comes back with your GKI and its zone. Read any metric’s history or summarise how it moved.

log_glucose_ketone_pair log_health_reading get_latest_readings get_health_history get_health_trend

Twelve metrics, including weight, body measurements, blood pressure and sleep. These tools write real health data to your account.

Fasting

4 tools

Start a fast on any protocol, end the one that’s running, and ask where your streak stands.

start_fast end_fast get_fasting_status list_fasts

Training

5 tools

Find an exercise in the MET catalog, log the workout, and let metabomap estimate the burn from your latest weight. Steps too.

log_workout search_exercise_types list_workouts get_activity set_steps

Supplements

5 tools

Search the supplement catalog, see what’s in your stack and what it contributes per day, start something new, change a dose, or stop.

search_supplements get_my_stack add_to_stack change_stack_dose end_stack_item

A stack item is a standing “I take this daily”, not a per-day log.

Meal plans and groceries

4 tools

Generate the week from your own recipes, read the plan back, get the shopping list grouped by store section, and log a planned meal once you’ve eaten it.

generate_meal_plan get_meal_plan get_grocery_list log_planned_meal

Generating replaces that week’s plan (locked meals survive) and needs macro goals in force.

Goals and diets

4 tools

Read the targets in force for a day, browse the diet catalog, save macro targets you’ve decided on, or pick a diet.

get_goals list_diets set_macro_goals select_diet

It saves targets you state. Working them out from your body data stays a wizard in the app.

In practice

Things people actually say.

Log 6 oz of ribeye and a cup of broccoli to dinner, then tell me what’s left.

Finds both foods in the catalog, logs them by weight, and reads the day back with your running totals against the day’s goals.

I just tested - glucose 88, ketones 2.1. Log those and tell me my GKI.

Records the two readings as one paired measurement and returns the Glucose Ketone Index with its zone. “How has my GKI moved this month?” works next.

Here’s the label on this protein bar - add it so I can log it.

Creates a private custom food from the panel, with your own serving sizes and its barcode. Net carbs are computed server-side, not guessed.

Draft a keto breakfast with eggs and cheddar and save it to my recipes.

Builds the recipe out of real catalog foods, so the per-serving nutrition is computed from data rather than recalled from memory. It lands in your recipe list.

Start an 18:6 fast, and what’s my streak?

Starts the fast on the 18-hour protocol and reports how many days you’ve strung together.

I did 40 minutes of bench press at 80 kg.

Finds the exercise in the MET catalog and logs it. Leave calories out and metabomap estimates them from your latest logged weight, and says that it estimated.

Permissions

It writes. So you decide what it may write.

We’re not going to pretend this is a read-only gadget. A connected assistant can log meals and readings, correct or delete entries, start a fast, and rebuild a week’s meal plan. That is the useful part, and it’s exactly why permissions are granted one at a time - reading your diary and writing to it are two separate decisions, and so are the seven other areas.

You approve them at the moment you connect, and a tool whose permission you didn’t grant doesn’t fail silently - it says which one is missing. Changed your mind? Delete the connector and it’s over in one click: the assistant no longer has metabomap in its hands, so it can’t call a single one of these tools again.

What no connection can ever reach

Some things aren’t on the menu at any permission level, because anything nobody deliberately granted is refused by default:

  • Your account, profile, and billing
  • Making more keys or connections
  • Community forums and challenges - anything that posts under your name
  • Connecting or disconnecting third-party accounts
  • Anything administrative

A connection can never mint another connection or another key - so it can’t widen its own reach behind your back, and one you delete stays gone.

Free to connect. On any plan.

Connecting Claude costs nothing on any plan, and it runs on the AI subscription you already have. Start a free metabomap account, paste one URL, and tell it what you had for breakfast.

Fair questions

Do I need to pay for this?

Connecting Claude is free on any plan - nothing to buy, no key, and it runs on the AI subscription you already have. API keys are the Premium part: they’re what you use for your own scripts, and for clients that can’t sign in yet, which today includes Codex. Keys are free for everyone during early access and move into Premium when payments open - you’re reading the announcement. If we get Codex signing in without a key first, connecting Codex becomes free too, and we’ll say so here.

What can it actually change?

A lot, which is the point - and why the permissions are granular. It can log food, water, workouts, supplements and health readings, edit or delete diary entries, start and end fasts, save macro targets, pick a diet, and build a week’s meal plan. It is not a read-only assistant. You choose which of those it may do when you connect, each one separately - so if you only want it reading your diary and never writing to it, that’s a setting, not a hope. And deleting the connector ends it: no connector, no tool calls.

Can it see my whole account?

Only the parts you grant, and some parts are never available to any connection at all: your profile and billing, key management itself, community posting, third-party account connections, and everything administrative. Those are refused by default rather than case by case - a field nobody deliberately granted is denied to every connector.

Does it work with ChatGPT, or only Claude and Codex?

The connector is a standard MCP server over HTTPS, so any client that supports remote MCP servers with sign-in can use it - we document Claude and Codex because those are the ones we test. There is nothing metabomap-specific in the handshake.

Is my food log being sent to train an AI model?

Not by us. The assistant is yours, running under your own AI subscription, and metabomap just answers its requests about your account. What your AI provider does with your conversation is governed by your agreement with them - which is exactly why we built it this way instead of putting a chatbot in the middle.

What does it do that the app doesn’t?

Nothing, and that’s deliberate - it’s the same account and the same rules, reached a different way. The difference is speed and hands: describing a meal out loud beats searching for four ingredients, and asking “how did my magnesium look last month?” beats navigating to the report. The app is still there for everything you’d rather see than say.

Told you first

One email when checkout opens, plus the occasional label-math finding worth two minutes. If the AI connector changes - new tools, or the line between free and Premium moving - you hear it here before you hear it from a locked button.

No ads, no pixels, no sharing your address. Unsubscribe anytime.