Cronometer MCP server Let your AI agent log your Cronometer diary.

ToolWhat it doesAccess

• get_diary_day Everything logged on one day: foods by Diary group, exercise, biometrics, notes and the day totals. read

  Returns one day of the diary as Cronometer shows it. Foods come grouped by the Diary groups of your account, in the order of the diary, with amount, calories and protein per entry and the day totals. Each entry has an entry_id that delete_entry takes. Dates are in the account time zone. An empty day returns empty groups and zero totals.

  MCP callcronometer_read → get_diary_day

  REST endpointGET https://cotlet.dev/api/v1/cronometer/diary-day

  Parameters

  Parameters: get_diary_day

  Name	Type	Description
  date date	date	The day to read, YYYY-MM-DD. Default: today.

  Example response

  {
    "date": "2026-11-05",
    "groups": [
      {
        "group": "Breakfast",
        "entries": [
          {
            "entry_id": "e1f20a",
            "food": "Oatmeal with berries",
            "amount": "1 bowl",
            "calories": 320,
            "protein_g": 12
          }
        ]
      },
      {
        "group": "Lunch",
        "entries": [
          {
            "entry_id": "e1f20b",
            "food": "Chicken and rice bowl",
            "amount": "1 bowl",
            "calories": 540,
            "protein_g": 46
          }
        ]
      },
      {
        "group": "Dinner",
        "entries": [
          {
            "entry_id": "e1f20c",
            "food": "Salmon with potatoes",
            "amount": "1 plate",
            "calories": 410,
            "protein_g": 35
          }
        ]
      }
    ],
    "exercise": [],
    "biometrics": [
      {
        "name": "Weight",
        "value": 72.4,
        "unit": "kg"
      }
    ],
    "notes": [],
    "totals": {
      "calories": 1270,
      "protein_g": 93
    }
  }

• search_foods Search the Cronometer food database and your custom foods by name. read

  Returns up to 20 matches for the query, your custom foods first, then database foods. Each match has a food_id for log_food, the serving sizes Cronometer offers and the calories of the default serving. Matches carry the source shown in the app, so you can tell a verified food from a user-made one.

  MCP callcronometer_read → search_foods

  REST endpointGET https://cotlet.dev/api/v1/cronometer/foods/search

  Parameters

  Parameters: search_foods

  Name	Type	Description
  query string required	string	Food name, for example grilled chicken breast.
  limit integer	integer	1 to 20. Default: 20.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "foods": [
      {
        "food_id": "f81d20",
        "name": "Chicken breast, grilled",
        "source": "Database",
        "default_serving": "100 g",
        "calories": 165
      },
      {
        "food_id": "f81d27",
        "name": "Rice, brown, cooked",
        "source": "Database",
        "default_serving": "1 cup",
        "calories": 218
      }
    ]
  }

• list_custom_foods Your custom foods, meals and recipes with calories and protein per serving. read

  Returns the custom foods saved in your account, newest first, with food_id, serving size, calories and protein. Use food_id with log_food. Only your own items are listed; foods shared by other users are not.

  MCP callcronometer_read → list_custom_foods

  REST endpointGET https://cotlet.dev/api/v1/cronometer/custom-foods

  Parameters

  Parameters: list_custom_foods

  Name	Type	Description
  query string	string	Only foods whose name contains this text.

  Example response

  {
    "foods": [
      {
        "food_id": "c2a901",
        "name": "Overnight oats",
        "serving": "100 g",
        "calories": 380,
        "protein_g": 14
      },
      {
        "food_id": "c2a8f4",
        "name": "Protein shake",
        "serving": "1 scoop",
        "calories": 120,
        "protein_g": 24
      }
    ]
  }

• log_food Add a food to a Diary group on a day, with an amount. write

  Adds one entry to your diary and returns it with its entry_id and the new day totals. food_id comes from search_foods or list_custom_foods. group is the name of a Diary group in your account; an unknown name fails and the error lists your groups. Nothing reaches other people and delete_entry removes the entry in one call, so it needs no confirmation by default.

  MCP callcronometer_write → log_food

  REST endpointPOST https://cotlet.dev/api/v1/cronometer/foods/{food_id}

  Parameters

  Parameters: log_food

  Name	Type	Description
  food_id string required	string	Food id from search_foods or list_custom_foods.
  amount number required	number	Amount in the unit below.
  unit string required	string	A serving unit Cronometer offers for that food, for example g or cup.
  group string required	string	Name of a Diary group, as shown in your diary.
  date date	date	Day to log to, YYYY-MM-DD. Default: today.

  Example input

  {
    "food_id": "f81d20",
    "amount": 150,
    "unit": "g",
    "group": "Lunch",
    "date": "2026-11-05"
  }

  Example response

  {
    "entry_id": "e1f20d",
    "date": "2026-11-05",
    "group": "Lunch",
    "food": "Chicken breast, grilled",
    "amount": "150 g",
    "calories": 248,
    "day_total_calories": 1518
  }

• create_custom_food Save a custom food with a serving size and nutrients, to log later. write

  Creates a custom food in your account and returns its food_id. It is private to you and is not shared. Calories are required; other nutrients you leave out stay empty, never zero. It reaches no one, and the food can be deleted in Cronometer, so it needs no confirmation by default.

  MCP callcronometer_write → create_custom_food

  REST endpointPOST https://cotlet.dev/api/v1/cronometer/custom-foods

  Parameters

  Parameters: create_custom_food

  Name	Type	Description
  name string required	string	Name of the food.
  serving string required	string	Serving size, for example 100 g.
  calories number required	number	Calories per serving.
  protein_g number	number	Protein per serving, grams.
  carbs_g number	number	Carbohydrates per serving, grams.
  fat_g number	number	Fat per serving, grams.

  Example input

  {
    "name": "Jane Doe",
    "serving": "serving",
    "calories": 1
  }

  Example response

  {
    "food_id": "c2a901",
    "name": "Overnight oats",
    "serving": "100 g",
    "calories": 380,
    "protein_g": 14
  }

• delete_entry Remove one diary entry by id: a food, exercise, biometric or note. write

  Deletes the single entry with that entry_id and returns what was removed. It never deletes a whole day or a custom food. Run get_diary_day or one of the list tools first to find the id. The entry is private to your account, so no one else is affected, and you can log it again, so it needs no confirmation by default.

  MCP callcronometer_write → delete_entry

  REST endpointDELETE https://cotlet.dev/api/v1/cronometer/entries/{entry_id}

  Parameters

  Parameters: delete_entry

  Name	Type	Description
  entry_id string required	string	Entry id from get_diary_day or a list tool.
  type enum required	enum	food, exercise, biometric or note.

  Example input

  {
    "entry_id": "entry_8c41d2",
    "type": "food"
  }

  Example response

  {
    "deleted": true,
    "entry_id": "e1f20d",
    "type": "food",
    "food": "Chicken breast, grilled",
    "date": "2026-11-05"
  }

ToolWhat it doesAccess

• get_nutrition_summary Daily nutrient totals for a date range, one row per day, with the target for each nutrient. read

  Returns one row per day between start and end, oldest first, with the totals of the nutrients you ask for and the target set for each. A day with nothing logged is returned with zero totals so gaps are visible. On the free plan Cronometer limits reports and charts to a 7-day window, and Gold removes that limit, so longer ranges need Gold.

  MCP callcronometer_read → get_nutrition_summary

  REST endpointGET https://cotlet.dev/api/v1/cronometer/nutrition-summary

  Parameters

  Parameters: get_nutrition_summary

  Name	Type	Description
  start date required	date	First day, YYYY-MM-DD.
  end date required	date	Last day, YYYY-MM-DD.
  nutrients string[]	string[]	Nutrient names as Cronometer shows them, for example calories, protein, fibre. Default: calories and protein.

  Example input

  {
    "start": "2026-10-01",
    "end": "2026-10-01"
  }

  Example response

  {
    "nutrients": [
      "calories",
      "protein_g"
    ],
    "days": [
      {
        "date": "2026-11-03",
        "calories": 1980,
        "protein_g": 121
      },
      {
        "date": "2026-11-04",
        "calories": 2140,
        "protein_g": 98
      },
      {
        "date": "2026-11-05",
        "calories": 1270,
        "protein_g": 93
      }
    ],
    "targets": {
      "calories": 2000,
      "protein_g": 120
    }
  }

• get_targets Your calorie, macro and micronutrient targets as set in Cronometer. read

  Returns the custom targets of your account for energy, macros and micronutrients, as Cronometer lists them under your targets. If you use the Macro Scheduler (Gold), the targets differ by weekday and the call returns the ones for the date you pass. Read-only: targets are changed in Cronometer.

  MCP callcronometer_read → get_targets

  REST endpointGET https://cotlet.dev/api/v1/cronometer/targets

  Parameters

  Parameters: get_targets

  Name	Type	Description
  date date	date	Day to read targets for, YYYY-MM-DD. Default: today.

  Example response

  {
    "date": "2026-11-05",
    "targets": [
      {
        "nutrient": "Energy",
        "amount": 2000,
        "unit": "kcal"
      },
      {
        "nutrient": "Protein",
        "amount": 120,
        "unit": "g"
      },
      {
        "nutrient": "Fiber",
        "amount": 30,
        "unit": "g"
      }
    ]
  }

ToolWhat it doesAccess

• list_biometrics Biometric entries such as weight in a date range, newest first. read

  Returns biometric entries between start and end, newest first, with name, value, unit and the entry_id that delete_entry takes. name filters to one biometric as Cronometer names it. Custom biometrics appear only if the account is on Gold, which is where Cronometer lets you create them.

  MCP callcronometer_read → list_biometrics

  REST endpointGET https://cotlet.dev/api/v1/cronometer/biometrics

  Parameters

  Parameters: list_biometrics

  Name	Type	Description
  start date required	date	First day, YYYY-MM-DD.
  end date required	date	Last day, YYYY-MM-DD.
  name string	string	One biometric by its Cronometer name, for example Weight. Default: all.

  Example input

  {
    "start": "2026-10-01",
    "end": "2026-10-01"
  }

  Example response

  {
    "biometrics": [
      {
        "entry_id": "b7c301",
        "date": "2026-11-05",
        "name": "Weight",
        "value": 72.4,
        "unit": "kg"
      },
      {
        "entry_id": "b7c2ff",
        "date": "2026-10-29",
        "name": "Weight",
        "value": 72.9,
        "unit": "kg"
      }
    ]
  }

• log_biometric Add a biometric value, such as weight, on a day. write

  Adds one biometric entry and returns it with its entry_id. name must be a biometric your account has, as Cronometer shows it; a custom biometric exists only if you created it on Gold. An unknown name fails and the error lists your biometrics. It reaches no one and delete_entry undoes it in one call, so it needs no confirmation by default.

  MCP callcronometer_write → log_biometric

  REST endpointPOST https://cotlet.dev/api/v1/cronometer/biometrics

  Parameters

  Parameters: log_biometric

  Name	Type	Description
  name string required	string	Biometric name, for example Weight.
  value number required	number	The value, in your account unit for that biometric.
  date date	date	Day, YYYY-MM-DD. Default: today.

  Example input

  {
    "name": "Jane Doe",
    "value": 1
  }

  Example response

  {
    "entry_id": "b7c302",
    "date": "2026-11-05",
    "name": "Weight",
    "value": 72.4,
    "unit": "kg"
  }

• list_exercises Exercise entries in a date range, newest first, with duration and calories burned. read

  Returns the exercise entries between start and end, newest first, with name, minutes and calories burned. Workouts synced from a device and entries you logged by hand are both listed. Each has an entry_id that delete_entry takes.

  MCP callcronometer_read → list_exercises

  REST endpointGET https://cotlet.dev/api/v1/cronometer/exercises

  Parameters

  Parameters: list_exercises

  Name	Type	Description
  start date required	date	First day, YYYY-MM-DD.
  end date required	date	Last day, YYYY-MM-DD.

  Example input

  {
    "start": "2026-10-01",
    "end": "2026-10-01"
  }

  Example response

  {
    "exercises": [
      {
        "entry_id": "x4410",
        "date": "2026-11-04",
        "name": "Running",
        "minutes": 35,
        "calories_burned": 360
      }
    ]
  }

• log_exercise Add an exercise entry with minutes on a day. write

  Adds one exercise entry and returns it with its entry_id. Calories burned come from Cronometer unless you pass calories_burned. It reaches no one and delete_entry undoes it in one call, so it needs no confirmation by default.

  MCP callcronometer_write → log_exercise

  REST endpointPOST https://cotlet.dev/api/v1/cronometer/exercises

  Parameters

  Parameters: log_exercise

  Name	Type	Description
  name string required	string	Exercise name, for example Running.
  minutes integer required	integer	Duration in minutes.
  calories_burned number	number	Override the calories Cronometer estimates.
  date date	date	Day, YYYY-MM-DD. Default: today.

  Example input

  {
    "name": "Jane Doe",
    "minutes": 1
  }

  Example response

  {
    "entry_id": "x4411",
    "date": "2026-11-05",
    "name": "Running",
    "minutes": 35,
    "calories_burned": 360
  }

• list_notes Diary notes in a date range, newest first. read

  Returns the notes you wrote on diary days between start and end, newest first, with the entry_id that delete_entry takes. Notes are plain text.

  MCP callcronometer_read → list_notes

  REST endpointGET https://cotlet.dev/api/v1/cronometer/notes

  Parameters

  Parameters: list_notes

  Name	Type	Description
  start date required	date	First day, YYYY-MM-DD.
  end date required	date	Last day, YYYY-MM-DD.

  Example input

  {
    "start": "2026-10-01",
    "end": "2026-10-01"
  }

  Example response

  {
    "notes": [
      {
        "entry_id": "n0921",
        "date": "2026-11-04",
        "text": "Slept badly, skipped the morning run."
      }
    ]
  }

• add_note Add a text note to a diary day. write

  Adds one plain-text note to the day and returns it with its entry_id. Notes are private to your account. It reaches no one and delete_entry undoes it in one call, so it needs no confirmation by default.

  MCP callcronometer_write → add_note

  REST endpointPOST https://cotlet.dev/api/v1/cronometer/notes

  Parameters

  Parameters: add_note

  Name	Type	Description
  text string required	string	The note.
  date date	date	Day, YYYY-MM-DD. Default: today.

  Example input

  {
    "text": "text"
  }

  Example response

  {
    "entry_id": "n0922",
    "date": "2026-11-05",
    "text": "Felt full after lunch, added a snack later."
  }