Talk to your roast log from your phone

Connect Claude, ChatGPT or any MCP app to your BrewedLate account and talk to it after a cup. What you say is not just written down: it is filed as a cupping or a brew on the right roast of the right green coffee, with the rest day and the recipe. The agent answers from that history (which roast of this bean was good, how you brewed it last time, how much green coffee is left), sorts roast from brew from rest and suggests one change. It can also log a roast or plan the next one for you.

Claude iOS: asked how roast 143 was last brewed, the agent finds no brew logged and reads the roast and its cup note.Claude iOS: a dictated brew description, 64 clicks, 15 g to 240 g, boiling water, a little dryness and sourness as it cools.Claude iOS: the agent suggests changes for dryness, sourness as it cools and muted fruit, and asks which roast this was.Claude iOS: after the user says to log it, the agent adds the roast to the cellar and records the brew.

Talk it through. It’s on the record.

A sour cup could be the roast, the brew or the rest. Home cupping notes are what tell them apart, and they are what nobody keeps up. With BrewedLate you just talk, and every note lands where the next decision needs it.

  1. 1

    Say it

    After a cup, tell the coffee agent on the site, Claude or ChatGPT how it tasted and how you brewed it. Your phone’s dictation is enough.

  2. 2

    It is filed

    Each cupping is stored on the right roast of the right green coffee, with the rest day, the recipe and whether it was good. A chat app on its own forgets; BrewedLate keeps the record.

  3. 3

    The next cup starts there

    Before the next brew or roast it reads every note on that bean, sorts roast from brew from rest, and suggests one change.

Ten days of our own cuppings, as they were logged

Spoken into Claude on a phone after each cup. Why this gets you out of the death spiral.

R-142 · Colombia Pacamara, natural

Roast or brew?

  1. 15 Oct · Day 9 of restFault

    V60, 15 g to 240 g, boiling water. Fruit and sweetness, but a sour-bitter edge. Not sure if it is roast or brew.

  2. 15 Oct · Day 9 of rest

    Suspect the boiling water, not the roast. Next test: 93 °C, nothing else changed.

  3. 17 Oct · Day 11 of restGood

    Water off the boil for 30-50 seconds. The sour-bitter edge is gone, which points to water temperature rather than the roast.

One change at the kettle, no roast spent: the roast was fine.

R-148 · Colombia SL28, natural

Or the rest?

  1. 21 Oct · Day 9 of rest

    Fruit less pronounced than usual for this bean, bitter and astringent. Earlier SL28 cups (R-131, R-111) were smooth, sweet and fruity.

  2. 21 Oct · Day 9 of rest

    Extra careful with agitation. Still slightly unpleasant: sour, bitter, astringent, fruit not pronounced.

  3. 24 Oct · Day 12 of restGood

    First sip incredibly fruity, like strawberry yoghurt. Aftertaste a little astringent. Much better than the day-9 brews.

Same roast, three more days of rest.

Part of BrewedLate Pro

Pro is $9 a month or $79 a year in US dollars, with a 14-day free trial. It gives you three things:

  • Claude, ChatGPT or any MCP app on your account, set up below.
  • The in-app coffee agent, if you would rather not connect an app.
  • Unlimited AI roast plans (a free account gets 3).

Everything else on BrewedLate stays free.

Create an account to start

14-day free trial, then billed in US dollars. Cancel any time.

See pricing

Set up in your AI app

BrewedLate is a standard remote MCP server, so any app that can add one works. This is the server URL:

/api/mcp

Claude (phone and desktop)

  1. In Claude, open Settings, then Connectors, and add a custom connector with the server URL below.
  2. Sign in to BrewedLate when asked, choose what Claude may do and approve.
  3. The connector belongs to your Claude account, so the app on your phone has it too: start a chat, press Talk and say how the cup tasted.

ChatGPT

  1. In ChatGPT, open Settings, then Apps & Connectors, and create a connector with the server URL below.
  2. Sign in to BrewedLate when asked, choose what ChatGPT may do and approve.
  3. Start a chat on your phone or computer and say how the cup tasted.

Other MCP clients

  1. In your agent, add a remote MCP server with the server URL below.
  2. Sign in to BrewedLate when asked, then choose what the agent may do and approve.

What your agent can do

Reading and writing are separate permissions. You choose both when you approve the connection.

Read

  • Dashboard get_dashboard

    Overview of your setup as JSON: roasting style preference, gear, active cellar (up to 50), green coffees (up to 50) and your 5 most recent roasts with their tasting. Start here.

  • List green coffees list_green_coffees

    Your green coffee inventory as a short list, { items }: id, name, origin, process, grams remaining and flags (empty, lowStock, beanComplete, canPlan). Optional search (part of the name, any case) and inStock (leaves out beans with 0 g). A bean that is only a name (from an imported roast log) has null origin, process and weight. Use get_green_coffee for the full record.

  • Get green coffee get_green_coffee

    One green coffee from your inventory by id, with purchase details, notes, roast goals and flags.

  • Roast context for a bean get_roast_context

    Everything needed to plan the next roast of one green coffee, as JSON: the bean and its goals, its roasts (newest first, up to 50) with metrics, roast tastings, and each roast's brews (up to 8, with recipe, days of rest and verdict), up to 5 good roasts on similar beans, and the profile catalogue ordered by fit (the order is not a recommendation). Needs the bean's origin and process; without them it answers VALIDATION_ERROR.

  • Find similar coffees find_similar_coffees

    Your past beans that resemble one coffee, as JSON (up to 5). Give greenCoffeeId, or origin with optional process, variety and altitude; not both. Each bean has its roasts (newest 8, oldest first) with tasting and brews (up to 4 per roast), how it matches (origin, process, variety, altitude) and where it differs, its last good roast and its validated recipe. A natural and an anaerobic of the same origin match on origin and differ on process. Use it to see what worked on an earlier coffee.

  • Find profiles by end temperature and hot zone find_profiles

    The profile and level pairs whose file reaches a target, as JSON (up to limit, default 8, max 20), nearest first. Searches the built-in profiles, your uploads and the public library over levels 1.0-5.0 in 0.1 steps. Give a target end temperature (endTempC) and/or hot zone (hotZoneSeconds), or fromRoast (a batch number) plus endTempChangeC and/or hotZoneChangeSeconds relative to its profile file's numbers at its level; not both. Each row has the predicted end temperature, total time, hot zone and time after first crack as the profile is drawn, how far it misses, the source (library rows: pagePath has the .kpro to load on the roaster first), your roasts on it with tasting counts, and whether it falls in your good window's designed range (greenCoffeeId, or the roast's bean). If nothing is inside the tolerance, items is empty and nearestMiss is the closest. onlyRoasted keeps profiles you have roasted.

  • List roasts list_roasts

    Your roasts, newest first, as { total, items }. Each item has numbers, not strings: roastLevel is Kaffelogic 1.0-5.0, higher is darker. Roasts imported from a log may have a null green coffee and a null roast date (undated roasts come last). Optionally filter by green coffee or status. Paginated: limit defaults to 20 (max 50), offset to 0. Use get_roast for the log metrics and cup notes of one roast.

  • Get roast get_roast

    One roast by its batch number (batchNumber, e.g. R-147, the number shown in the app) as { roast, metrics, diagnostics, cupNotes }: the roast as list_roasts shows it (roastLevel is Kaffelogic 1.0-5.0, higher is darker), its roast log metrics, automatic diagnostics and your cup notes. A roast imported from a log may have no green coffee and no roast date (null). The raw log is never returned.

  • List cup notes list_cup_notes

    Your cup notes as { items }, newest first (max 50, default 20). Filter by greenCoffeeId (notes on any roast of that bean), batchNumber (a roast, e.g. R-147), cellarEntryId, a date range (from and to, YYYY-MM-DD NZ calendar days, both included; every note carries its `day`) and result (good or fault). Each note names its roast by roastBatchNumber (null for a note on a cellar entry with no roast). Use it to find the id of a note before update_cup_note.

  • Roast analytics for a bean get_roast_analytics

    One comparison row per finished roast of a green coffee, as { items }: profile, level (Kaffelogic 1.0-5.0, higher is darker), weight loss, drop temperature and tasting result.

  • List roast profiles list_roast_profiles

    The Kaffelogic roast profiles known to the app (no curves; levels are Kaffelogic 1.0-5.0, higher is darker), whether you have used each, the profiles you uploaded, plus profile codes you use that are not in the registry.

  • Supply forecast get_supply_forecast

    How much roasted coffee is ready or resting, when stock runs out, when to roast next and how much green to use, with the settings behind it.

  • List cellar list_cellar

    Your cellar as { items }, one summary per coffee (scope active, archived, consumed or all): name, roaster, origin, roastLevel (a home roast's is the Kaffelogic level 1.0-5.0, higher is darker; a bought coffee's is the roaster's label), batchNumber (a home roast), current recipe, next brew (the recipe planned for next time, with why), brew count and flags. Each entry's handle is cellarEntryId (for get_cellar_entry, record_brew and set_cellar_entry_state). No brew history.

  • Get cellar entry get_cellar_entry

    One cellar entry by id (a home roast's roastLevelValue / roastLevel is the Kaffelogic level 1.0-5.0, higher is darker) with its current recipe, its next brew (planned for next time, with why), your most recent brew iterations (iterationLimit defaults to 20, max 50), the total iterationCount and your cup notes.

  • List gear list_gear

    Your brewing gear as { items }: grinders, brewers, kettles and which is the default.

  • Search coffees search_coffees

    Find in-stock coffees in the catalogue by name (query, at least 2 characters; limit defaults to 10, max 25). Returns { items }, each with id, name, roasterName, origin, process and roastType. Use the id with add_coffee_to_cellar.

  • Get guide get_guide

    One BrewedLate domain guide as { name, text }, text in markdown. name roast-profile-selection: how to choose a Kaffelogic profile and level and adjust after a roast; read it before proposing a roast. name brewing-reference: grinder ranges, process and origin patterns, recipe scaling and troubleshooting. name troubleshooting: how to tell a roast fault from a brew fault when a coffee is not right.

Write

  • Add green coffee add_green_coffee

    Add a green coffee to your inventory. Remaining grams start at weightGrams.

  • Update green coffee update_green_coffee

    Change fields of one green coffee by id, including its roast goals (targetRoastLevel, targetFlavorProfile, roastGoals). Send null for notes, region or variety to clear it.

  • Plan a roast plan_roast

    Save a planned roast for one green coffee. Does not use up green coffee until the plan becomes a roast (update_roast). profileCode must be a code from list_roast_profiles or one you have used. Roast level is the Kaffelogic scale, 1.0 to 5.0, where higher is darker (2.4 is darker than 2.2). greenWeightGrams defaults to 120 per batch or what remains, whichever is less. A roast is one jar: batchCount (1-4) is how many machine batches of the same recipe went into it, and greenWeightGrams is the jar total (two batches of 100 g: batchCount 2, greenWeightGrams 200).

  • Log a roast log_roast

    Record a roast you have done (saved as roasted). Deducts greenWeightGrams from the green coffee, and fails if less remains. profileCode, when given, must be a code from list_roast_profiles or one you have used. Roast level is the Kaffelogic scale, 1.0 to 5.0, where higher is darker (2.4 is darker than 2.2). A roast is one jar: batchCount (1-4) is how many machine batches of the same recipe went into it, and greenWeightGrams is the jar total (two batches of 100 g: batchCount 2, greenWeightGrams 200).

  • Update a roast update_roast

    Change fields of one roast by its batch number (batchNumber, e.g. R-147, the number shown in the app). Moving a planned roast to roasted, failed or consumed makes it a real roast and deducts its green weight once, and fails if less remains. Changing the green weight of a recorded roast moves the difference in the stock of the green coffee. batchCount is how many machine batches went into the jar (greenWeightGrams is the jar total); it cannot drop below the logs the roast holds. profileCode, when given, must be a code from list_roast_profiles or one you have used. Roast level is the Kaffelogic scale, 1.0 to 5.0, where higher is darker (2.4 is darker than 2.2).

  • Add roast to cellar add_roast_to_cellar

    Add one roast, named by its batch number (batchNumber, e.g. R-147), to your cellar (My Brews). Repeating the call returns the cellar entry already made for that roast. Not needed before record_brew.

  • Add cup note add_cup_note

    Record how a roast or cellar coffee tasted: a result (good or fault, with fault types), notes, an optional score 1-100 and brew method. Only the result counts as the tasting verdict; a note without one leaves the roast untasted. Needs batchNumber (the roast, e.g. R-147) or cellarEntryId. One note per tasting: only for a cup with no recipe, refused as DUPLICATE when the same coffee got a chat note in the last 30 minutes. To correct a note, call update_cup_note (find it with list_cup_notes). To log a brew with its recipe (dose, grind, water, ratio), call record_brew on the roast, not a cup note. brewTaste: how the brew was off (sour, bitter, weak, strong, sour-weak, sour-strong, bitter-weak, bitter-strong, or dry); a fault with only a brew taste does not count against the roast. A good cup the user calls astringent, dry, bitter, sour, weak or strong stays good and gets that brewTaste.

  • Keep a lesson save_lesson

    Keep one short lesson (up to 280 characters) about a green coffee, for example "Lots of fines: a coarser grind, 96 C at 1:15 worked". Show the user the exact text and get their confirmation first. Optionally name the roast it came from (roastBatchNumber, e.g. R-147, on that coffee). Not idempotent: every call adds a lesson. The lessons come back in get_roast_context and find_similar_coffees.

  • Make a profile variant create_profile_variant

    Make a copy of one roast profile with ONE dial moved and keep it as the user's own profile: dial "start" (time to 150 C), "middle" (150 C to 200 C) or "hotZone" (200 C to the end) with by in seconds, or "endTemp" with by in C (the hot zone stays as it was); a negative by shortens or lowers. Everything else stays as the profile is drawn, so the next roast tests that one change. profileCode is a built-in profile or one the user uploaded (list_roast_profiles); level is the level they roast it at (default: the profile's recommended level). A phase can change to 60-160% of its length, the end temperature by up to 8 C. Answers the new profile code and the phases before and after. Ask once for both steps, then do both: make the variant and plan_roast on the new code at the same level, so all the user has left to do is download the file and load it on the roaster before roasting: give them downloadPath as a link on this site (it offers that one file to them once signed in). Use it when level changes did not move the roast (get_roast_context: the same hot zone and drop temperature across roasts) or a rested cup needs one phase changed; say which dial and why, and get confirmation first. Repeating the call answers the variant already made.

  • Send feedback send_feedback

    Send product feedback to the BrewedLate developer. Show the user the exact text and send only after they agree. Up to 2000 characters; category is bug, missing_data, confusing_tool, idea or null. Not idempotent: every call sends one item, at most 10 per day.

  • Update cup note update_cup_note

    Change one of your cup notes by id (find it with list_cup_notes). Use this to correct a tasting instead of adding a second note. Sending result sets faults and brewTaste together (no brewTaste clears it). brewTaste: how the brew was off (sour, bitter, weak, strong, sour-weak, sour-strong, bitter-weak, bitter-strong, or dry); a fault with only a brew taste does not count against the roast.

  • Update supply settings update_supply_settings

    Change the settings behind the supply forecast: dailyConsumptionGrams, restDays, targetBufferDays. At least one.

  • Set roasting preference set_roasting_preference

    Replace your roasting style preference, the free text shown in get_dashboard and used when planning roasts.

  • Add coffee to cellar add_coffee_to_cellar

    Add a coffee you bought to your coffees: either coffeeId from search_coffees (repeating the call returns the entry already made) or coffee, a described coffee not in the catalogue (name required). Pass exactly one. Returns the cellar entry; its id is the cellarEntryId for record_brew.

  • Record a brew record_brew

    Log a brew of one of your coffees: pass roastBatchNumber (e.g. R-147) for a roast, or cellarEntryId for a coffee you added (a bought bag), exactly one. The recipe used, optional notes and score (1-100) which become a cup note, optional result (good or fault) with faults (a fault needs a roast fault type or a brewTaste; faults are only allowed for a fault), optional negative feedback. brewTaste: how the brew was off (sour, bitter, weak, strong, sour-weak, sour-strong, bitter-weak, bitter-strong, or dry); a fault with only a brew taste does not count against the roast. A good cup the user calls astringent, dry, bitter, sour, weak or strong stays good and gets that brewTaste. A brew with notes, score or result IS the tasting: do not also call add_cup_note for it. temperatureC is required: when not measured, give your best estimate (off the boil about 30-60 s is 93-95 C) and say so in recipe.notes ("not measured: off the boil ~40 s"). A brew without feedback and without a fault becomes the coffee's current recipe. Only a coffee from the catalogue can be published as a public recipe; a home roast never is. Optional nextBrew ({ recipe, reason } up to 280 characters): the recipe the user agreed to try next time, shown on the roast in the app; without it the brew clears the coffee's earlier next brew.

  • Correct a saved brew update_brew

    Correct a brew you already saved (iterationId from get_cellar_entry): change its recipe, notes, score, result, faults or brewTaste (the same rules as record_brew), and/or move it to another coffee with roastBatchNumber (e.g. R-153) or cellarEntryId, at most one. Use this when a brew was filed on the wrong roast: the brew takes the next number on the target, its cup note and verdict move with it, and both coffees' current recipes are recomputed. Send only what changes. It leaves the next brew alone. Not for a new brew (record_brew) or a cup note without a brew (update_cup_note).

  • Delete a saved brew delete_brew

    Delete one saved brew (iterationId from get_cellar_entry), for example a duplicate. Its cup note goes with it, so the roast's verdict stops counting it, and the coffee's current recipe falls back to its latest remaining brew. A brew filed on the wrong roast should be moved with update_brew instead. Cannot be undone.

  • Set the next brew set_next_brew

    Save the recipe the user agreed to try next time they brew a coffee, with one short reason (up to 280 characters, e.g. "Bright but thin: one click coarser"): roastBatchNumber (e.g. R-147) for a roast, or cellarEntryId, exactly one. It replaces any earlier next brew, records no brew, and the app shows it on the roast next to the last brew's recipe. When you are also logging the brew just made, pass nextBrew to record_brew instead. Recording the next brew clears it.

  • Set cellar entry state set_cellar_entry_state

    Set one cellar entry to active (in the cellar), archived (put away) or consumed (bag finished). Nothing is deleted.

What it cannot do

  • Delete roasts, beans, cup notes or your account. (With write access it can remove a brew you logged twice.)
  • Upload roast logs or photos.
  • See any other user's data.

Disconnect

Remove an agent any time under Connected apps on your account page.