---
name: cronch
description: Plan and track a person’s workday meals, water and breaks with Cronch, routed around their meetings. Use when the user asks what’s next today, wants to mark a meal or break done, snooze or skip something, log water, get food ideas for right now that fit their diet and allergies, add today’s meetings, replan the afternoon, change their Cronch setup, check their streak, or read a sign-in code from their Cronch inbox.
---

# Cronch

Cronch is a personal agent for developers that plans meals, water and breaks around your calendar and pings you when it’s time. Each item on the day’s plan is one action: done, snooze or skip. You act for a signed-in Cronch user, on their plan.

## When to use it

- The user asks what’s next, what’s left today, or how their day looks.
- They want to mark lunch done, skip a break, snooze a reminder or log a glass of water.
- They’re hungry now and want options that fit their diet, allergies, budget and how long they want to cook.
- Their meetings changed: tell Cronch so meals and pings move out of them, then replan.
- They want to change their setup: diet, allergies, work and quiet hours, ping cadence or water goal.
- They ask about their streak, meals kept or water this week.
- They ask for a sign-in code that arrived at their Cronch inbox.

## When not to use it

- Ordering or paying for food. Cronch only opens a search on Uber Eats, DoorDash or Google Maps; the user checks out themselves.
- Booking restaurant tables.
- Counting calories or macros, or medical and nutrition advice.

## Connect

1. **MCP (chat assistants and coding agents).** Remote server https://api.cronch.io/api/v1/mcp, Streamable HTTP. OAuth 2.1 with PKCE; discovery starts from the 401’s WWW-Authenticate header. Ask for `cronch:read` alone if you only read; `cronch:write` is needed to change the day. Clients without OAuth send `Authorization: Bearer cronch_pat_…`, a personal access token the user creates under Apps & MCP in the Cronch dashboard.
2. **REST.** https://api.cronch.io/api/v1 with the same personal access token. Every endpoint, schema and scope is in https://cronch.io/openapi.json.
3. **Try it first.** The sandbox needs no account or token and saves nothing: MCP at https://api.cronch.io/api/v1/sandbox/mcp, REST at https://api.cronch.io/api/v1/sandbox.

## Tools

| Tool | Scope | What it does |
| --- | --- | --- |
| `get_today` | read | Today’s plan: every meal, water and break job with its time, status and id, what’s next, progress and meetings. |
| `complete_item` | write | Mark a meal, water or break done. Defaults to the next open item. |
| `skip_item` | write | Skip an item without doing it. |
| `snooze_item` | write | Push an item later, 15 minutes by default. |
| `im_hungry` | write | Options for right now with recipe steps and Uber Eats, DoorDash and Google Maps search links. Never places an order. |
| `swap_meal` | write | Replace a planned meal with one that still fits diet, allergies and budget. |
| `log_water` | write | Record one glass of water. |
| `add_meetings` | write | Tell Cronch about today’s meetings in plain text so meals and pings route around them. |
| `replan` | write | Rebuild the rest of today, keeping what’s already done. |
| `ask_agent` | write | Plain-language requests to the Cronch agent. Slash commands like /hungry work too. |
| `get_history` | read | Streak, meals kept, water per day and breaks this week. |
| `get_profile` | read | Diet, allergies, cooking, budget, work and quiet hours, cadence and water goal. |
| `update_profile` | write | Change any of those; the rest of today is replanned around them. |
| `get_inbox` | read | Recent mail at your Cronch address. Codes stay masked unless you ask. |
| `get_latest_code` | read | The newest sign-in code at your Cronch address, only when you ask for it. |
| `read_message` | read | The full text of one inbox message. |
| `export_ics` | read | The rest of today as an .ics calendar file. |

## How to work with it

1. Call `get_today` first. Item ids from it, or `"next"`, drive `complete_item`, `skip_item`, `snooze_item` and `swap_meal`.
2. When meetings come up, call `add_meetings` with plain text like "standup 10:00, 1:1 15:30" rather than editing items one by one.
3. For "I’m hungry", call `im_hungry` with what the user said (time, cooking, cravings). Offer the recipe or the search links it returns.
4. Report what changed in a sentence: "Lunch is marked done. Next is water at 14:00."

## Rules

- Never say an order was placed or a table was booked. Food links only open a search.
- Sign-in codes are sensitive. Show one only when the user asks for it.
- A 402 with code `limit_reached` means today’s AI allowance is used up (agent, hungry and swap). It resets at midnight UTC; plan actions still work.
- Over REST, send an `Idempotency-Key` header on writes you might retry, so a retry doesn’t log water twice.
- Respect rate limits: on 429, wait for `Retry-After` seconds.

## More

- Developer docs: https://cronch.io/docs
- Setup for each app: https://cronch.io/mcp
- Everything about Cronch for language models: https://cronch.io/llms.txt
- Help: support@cronch.io