[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

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

> Cronometer has no public API (checked 6 Nov 2026). Its Pro FAQ says Everfit, Kalix and Practice Better have access to its API and that select nutrition data can be reached through those platforms. We found no official Cronometer MCP server and no Cronometer app for Claude or ChatGPT. Cotlet runs 14 Cronometer tools hosted, over MCP for agents and REST for scripts, in your own login with no API key from Cronometer.

Tell your agent what you ate and it finds the foods and logs them to the right Diary group in Cronometer. It also reads your nutrient totals and targets, and adds weigh-ins, exercise and notes. It works inside Claude and ChatGPT, with no developer setup.

- Free 7-day trial, no card
- Unofficial, not affiliated with Cronometer
- Page: https://cotlet.dev/integrations/cronometer-api-mcp-server

## What can your AI agent do in Cronometer?

- Log meals you describe
- Save a recipe as a custom food
- Check protein and calories against targets
- Sum a week for a sheet
- Log weigh-ins and workouts
- Plan the rest of your day

## Does Cronometer have an MCP server or an API?

- Cronometer's partner platforms read select nutrition data. None of them logs food, creates custom foods or adds biometrics for you from code.
- Zapier has no Cronometer app, and n8n lists none.
- Free GitHub servers exist, for example rwestergren/cronometer-api-mcp (70 stars, MIT, last commit 2 Nov 2026). You install and run them on your own computer.

| What you need | Cronometer partner API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Read a day of your diary | Select data, via partners | Yes | Yes |
| Log food into your diary | Not offered | Yes | Yes |
| Open to an individual | Partners and Enterprise | Yes | Yes |
| Works in the Claude and ChatGPT apps | No connector | Yes, you run it | Yes, hosted |
| Nothing to install or host | Via a partner app | No | Yes |

Checked 6 Nov 2026. Sources: [Cronometer Pro FAQ](https://cronometer.com/blog/cronometer-pro-faq/), [Cronometer Gold and the free version](https://cronometer.com/gold/), [Cronometer community: public API requests](https://forums.cronometer.com/discussion/comment/21596), [GitHub: rwestergren/cronometer-api-mcp](https://github.com/rwestergren/cronometer-api-mcp)

## How does the Cronometer MCP server work?

1. **Sign in to Cronometer.** Use your own account in its Cotlet Cloud Browser.
2. **Connect your AI agent.** Add the Cotlet address to Claude or ChatGPT.
3. **Ask in plain words.** Say what you ate or what you want to know.

We never keep your Cronometer password, and no tool touches your payment, password or account.

## How to connect Cronometer to your AI agent

Pick your client in the tabs. The steps are the same everywhere.

1. **Turn Cronometer on for agents.** Create a Cotlet account, log in to Cronometer in its Cloud Browser, then press Enable for agents.
2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
3. **Sign in or use a key.** Claude and ChatGPT ask you to sign in to Cotlet. Cursor, Codex, n8n and scripts take an API key from the console.

One shared address, `https://cotlet.dev/mcp/v1`, carries Cronometer next to your other apps. If you enable Cronometer after connecting, refresh the connector so the new tools show up.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-cronometer \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-cronometer": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet-cronometer]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: cronometer_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: cronometer_write
```

## All 14 Cronometer MCP tools

### Diary and foods

Logging a food needs the food_id from a search and the name of one of your Diary groups. Every entry has an entry_id that delete_entry takes.

- **Get diary day** (`get_diary_day`, read): Everything logged on one day: foods by Diary group, exercise, biometrics, notes and the day totals.
- **Search foods** (`search_foods`, read): Search the Cronometer food database and your custom foods by name.
- **List custom foods** (`list_custom_foods`, read): Your custom foods, meals and recipes with calories and protein per serving.
- **Log food** (`log_food`, write): Add a food to a Diary group on a day, with an amount.
- **Create custom food** (`create_custom_food`, write): Save a custom food with a serving size and nutrients, to log later.
- **Delete entry** (`delete_entry`, write): Remove one diary entry by id: a food, exercise, biometric or note.

### Nutrient totals and targets

Cronometer limits free reports and charts to a 7-day window, so longer ranges need Gold (Cronometer Gold page, 6 Nov 2026). Targets are read only.

- **Get nutrition summary** (`get_nutrition_summary`, read): Daily nutrient totals for a date range, one row per day, with the target for each nutrient.
- **Get targets** (`get_targets`, read): Your calorie, macro and micronutrient targets as set in Cronometer.

### Biometrics, exercise and notes

Custom biometrics exist only if you created them on Gold. Weigh-ins use the unit of your account.

- **List biometrics** (`list_biometrics`, read): Biometric entries such as weight in a date range, newest first.
- **Log biometric** (`log_biometric`, write): Add a biometric value, such as weight, on a day.
- **List exercises** (`list_exercises`, read): Exercise entries in a date range, newest first, with duration and calories burned.
- **Log exercise** (`log_exercise`, write): Add an exercise entry with minutes on a day.
- **List notes** (`list_notes`, read): Diary notes in a date range, newest first.
- **Add note** (`add_note`, write): Add a text note to a diary day.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/cronometer-api-mcp-server#tools

## Who can see my Cronometer session, and how do I revoke it?

- **What we store.** Your logged-in Cronometer profile, encrypted with AES-256-GCM, in Finland. Not the password.
- **What your agent gets.** The 14 Cronometer tools. Never the cookie.
- **What the session sees.** Your diary, targets, biometrics, exercise, notes and custom foods.
- **What no tool touches.** Gold plan, payment, password, two-factor and deleting your account.
- **If Cronometer asks for a code.** The code prompt goes to you. You type it in, we never do.
- **How to cut access.** Disable for agents, reset the browser, or log out of Cronometer.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet.

## What happens when Cronometer changes?

- **12 h** between tests of the Cronometer tools
- **$0** for a call to a Cronometer tool paused for repair

When Cronometer moves a screen or renames a field, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes.

## Undo and mistakes

1. **Finds the food.** Searches your custom foods first, then the database.
2. **Picks a serving.** Uses a unit Cronometer offers for that food, like g or cup.
3. **Logs it.** Adds it to the Diary group and day you named.
4. **Reports the result.** Entry ID, calories and the new total for the day.

| Action | Undo |
|---|---|
| Log a food | delete_entry, one entry per call |
| Log exercise | delete_entry |
| Log a biometric | delete_entry |
| Add a note | delete_entry |
| Create a custom food | Delete it in Cronometer; it is private to you |

None of the 14 tools waits for your OK: every write lands in your own diary and reaches no one, and each one has an undo. Scheduled runs need no approval.

> A wrong day or serving is a diary edit, not a lost record. Ask the agent to fix the entry or delete it.

MCP call:

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

REST:

```
curl -X POST https://cotlet.dev/api/v1/cronometer/foods/f81d20 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":150,"unit":"g","group":"Lunch","date":"2026-11-05"}'
```

Tool output:

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

Scripts and cron jobs reach the same tools over REST at `/api/v1/cronometer`, with the same key and price. A failed call costs nothing. The tools table lists the REST path of each tool.

## How much does the Cronometer MCP server cost?

**About $34 a month** for logging 6 foods a day with a weigh-in, 5,820 credits. Your Cronometer plan is billed by Cronometer as before.

| Job | Calls | Credits |
|---|---|---|
| Log a day of meals from your words, daily | 13 × 30 | 3,900 |
| Log a weigh-in, daily | 1 × 30 | 300 |
| Weekly review: 7-day totals, targets, weights | 3 × 4 | 120 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 5,820 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on the free Cronometer plan too

The month is our example. Cronometer publishes no average for foods logged a day, so we assume 6, each with one search call and one log call, plus one diary check. The weekly review covers 7 days, the window Cronometer gives free reports. Dollars at the $29 pack rate.

## Cronometer MCP server on GitHub or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| [rwestergren/cronometer-api-mcp](https://github.com/rwestergren/cronometer-api-mcp) | 19 tools for food log, nutrition, food search, diary entries, custom foods, recipes, targets, fasting and biometrics. 70 stars, MIT, last commit 2 Nov 2026. | Runs on your computer. Claude on the web, your phone and ChatGPT need you to host it. |
| [cphoskins/cronometer-mcp](https://github.com/cphoskins/cronometer-mcp) | PyPI package with food log, micronutrients, diary entries, recurring foods, targets, fasting, biometrics and CSV export. 28 stars, MIT, last commit 1 Nov 2026. | Local, you keep it running. Its README asks for a Gold account. |
| [ekelly95/cronometer-mcp](https://github.com/ekelly95/cronometer-mcp) | npm package with the full diary, targets and writes with approval. 0 stars, MIT, last commit 18 Oct 2026. | Set up on your computer, single maintainer. |
| [cronometer-mcp.dev](https://cronometer-mcp.dev/) | Hosted remote server with 16 tools, sign-in in the browser, open source. | A third-party service; price not listed on the page. |
| [milldr/crono](https://github.com/milldr/crono) | Command line tool that quick-adds macros through browser automation. 44 stars, MIT, last commit 5 Nov 2026. | Not an MCP server, and it adds macros only. |

If you are happy to install a server and keep it running, a GitHub server is free. Cotlet is for people who want the same diary tools in Claude or ChatGPT with nothing to host, on any device, on a schedule if you like.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Cronometer tools.

## Cronometer MCP server: questions

### How do I connect Cronometer to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Cronometer once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Cronometer account through Cotlet, in their phone apps too.

### What can ChatGPT do in Cronometer?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Cronometer: log a meal from a plain description; weekly nutrition summary against targets; plan the rest of the day to hit protein. You ask in plain words, and anything that reaches other people waits for your OK first.

### How do I get access?

Create a free account at https://cotlet.dev, open Cronometer under Integrations in the console and log in to Cronometer in its Cloud Browser. The trial starts with your first app, no card asked.

### Do I need Cronometer Gold?

No for the diary tools. Cronometer lists logging of foods, exercise, biometrics and notes, custom targets, custom foods and recipes in the free version. Gold adds custom biometrics, timestamps and reports without the free 7-day window, so longer summaries and custom biometrics need Gold (Cronometer Gold page, checked 6 Nov 2026).

### Is there an official Cronometer API or MCP server?

Not a public one. As of 6 Nov 2026 the Cronometer Pro FAQ names Everfit, Kalix and Practice Better as platforms with API access, and we found no official MCP server. Cotlet gives you the diary tools in Claude or ChatGPT without a developer key.

### Does it use the Cronometer website?

Yes. Cotlet works in the Cronometer website in your own Cloud Browser, where the diary is at cronometer.com, so you need no app on the phone.

### Is the MCP server different from the REST API?

Only the door is different. Both expose the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

### Is Cotlet affiliated with Cronometer?

No. Cotlet is independent and not affiliated with Cronometer.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
