Plan dinners with Bryti from your own assistant: the week, shopping list, pantry and recipes.
Connect Remote server
claude mcp add --transport http bryti https://api.bryti.app/mcp{
"mcpServers": {
"bryti": {
"url": "https://api.bryti.app/mcp"
}
}
}{
"servers": {
"bryti": {
"type": "http",
"url": "https://api.bryti.app/mcp"
}
}
}Settings > Connectors > Add custom connector
URL: https://api.bryti.app/mcpTools 59 found in our last check
get_household_overviewRead the household's name, language and usual dinner time, who lives in it, their dietary constraints and their food preferences.
get_rulesRead the household's meal rules, and the national defaults that apply while it has none of its own.
get_week_planRead the dinner plan for the week starting at weekStart (a Monday), one page of days at a time.
get_inventoryRead what the household has at home: pantry, fridge and freezer, filtered and paged.
get_shopping_listRead the shopping list for the week starting at weekStart, or the current week without one: the week's dinners minus what is at home. The guide for putting it in an online store's cart is get_shopping_guide, and the shop_online prompt.
get_storesRead the stores the household shops in.
get_recipesSearch or list the household's recipes, paged; a search and the favourites also cover the shared starter library.
get_recipeRead one recipe by id: ingredients, steps and times.
get_dayRead one day: the dinner, its time, the calendar, meal events and the rules that apply.
get_planned_dinnerRead the planned dinner and its recipe for one date.
get_meal_eventsRead the household's meal events (guests, eating out, packed lunches) between two dates.
search_helpSearch Bryti's help articles.
search_tipsSearch Bryti's fact-checked kitchen tips.
get_calendar_eventsRead the household's calendar events between two dates.
get_shopping_guideReturns Bryti's guide, in the household's language, for putting the household's shopping list in an online store's basket. The member places the order.
get_planning_statusHow a planning run started by plan_week or replan_open_days is going: queued, running, done or failed, and how many days the week has planned once it is done. Without jobId, the household's latest run.
add_shopping_itemAdd one item to the shopping list for the week that holds weekStart. The week needs a plan.
check_shopping_itemTick an item off the shopping list (purchased=true) or put it back (purchased=false), by its name.
remove_shopping_itemRemove an item the household added by hand from the week's shopping list, by its name. Items the week's dinners need cannot be removed.
add_inventory_observationRecord what happened to a food at home: bought, seen, used, frozen, thrown out or gone.
add_guests_for_dateAdd guests for dinner on a date, or over several days with endDate. Name the household's usual guests in guestNames instead of counting them.
mark_eating_outMark that the household eats out on a date, or over several days with endDate. Planned dinners on unlocked days in the span are taken off the plan.
mark_awayMark the household away from home (a trip, the cabin) from date to endDate. Planned dinners on unlocked days in the span are taken off the plan.
set_dinner_timeMove when dinner is served on one evening (date, or today), or from now on for some weekdays.
set_prep_daysSet the weekdays the household preps ahead for the week, and the hour it starts. Steps a recipe allows to be done early are then shown on the latest prep day that keeps them fresh. An empty weekdays list turns prep days off. freezesPrep lets steps that keep frozen go to an earli…
replace_dinnerSwap the planned dinner on a date to another dish suggested for that day, by its title. A recipe from the household's library by its exact title also works, on a day nobody has planned yet too: the week opens around it. A title that does not match fails with the dishes to choose…
set_dinner_lockLock a day's dinner so replanning never changes it (locked=true), or unlock it.
set_recipe_favoriteMark a recipe as a favourite (favorite=true) or take the mark away, for the family or one member. Use the exact title from get_recipes.
import_recipe_from_urlBring a recipe from a web page into the household's recipes. Bryti reads the page; this uses some of the household's monthly credits. The import reads what can be made ahead from the page itself; get_recipe shows the timeline afterwards.
save_recipeSave a new recipe to the household's own recipes. Mark what can be made ahead (a sauce, a dough) in timeline, so it lands on the prep day.
record_outcomeRecord how a planned dinner went: made, made with changes, not made, or eaten elsewhere.
plan_weekPlan dinners for a week with Bryti's planner, inside the household's rules, events, allergies and pantry. The run is queued and takes one to three minutes; the answer carries a jobId — ask get_planning_status for it. A week that already has planned dinners answers confirmation_r…
replan_open_daysFill the open days of a week that already has a plan; dinners already planned, locked or answered stay where they are. Queued like plan_week; ask get_planning_status with the jobId. Uses the household's monthly credits.
clear_weekTake every dinner off a week and keep the plan, so it can be planned again at once. Days already passed and evenings out stay; a locked day stays unless includeLocked is true. The shopping list loses the recipe lines and keeps what the household added by hand. Ask the member fir…
set_category_for_dateAdd a rule for one date: the dinner should be of this category (Hard = must, Soft = preferably). The answer's undo deletes the rule again.
set_max_cooking_time_for_dateAdd a rule for one date: at most this many active minutes at the stove. The answer's undo deletes the rule again.
delete_ruleDelete one of the household's own meal rules by the id get_rules shows. National defaults are not rules of the household's own and cannot be deleted. Ask the member first: the answer's undo files the rule again, except a dinner time, the prep days or a rule over a range of dates.
set_leftover_dinnersWhether Bryti plans leftover dinners: about every third day, never on Friday or Saturday. A household setting, not a rule.
set_lunchbox_portionsSet how many extra portions one planned dinner cooks for the next day's lunchboxes, 0 to 10; without portions it follows the household's weekday setting again. Lunch is not planned: the extra portions are bought and cooked with the dinner. A dish that should not be heated again…
edit_recipeChange a recipe the household owns, found by its current title. Only the fields given change; ingredients, steps and timeline replace the whole list when given, so send them complete, as get_recipe shows them. Mark what can be made ahead in timeline, so it lands on the prep day.
delete_recipeDelete one of the household's own recipes, by its title. Built-in recipes cannot be deleted, and a recipe planned for a day ahead stays until that day has another dinner.
wish_dishPut a dish on the household's wish list, or add a vote when it is already there. A wish lifts the dish in the next planned week; it is a weight, never a rule. A title from get_recipes gives that recipe; any other name is kept as said.
adapt_dinner_ingredientMake one evening's dinner with something the household has instead of an ingredient, e.g. milk instead of cream. Only that evening changes, and the replaced ingredient leaves the shopping list; the recipe in the library stays as it is.
mark_member_absentMark that one member of the household is not home for dinner on a date, by the name get_household_overview shows.
delete_meal_eventRemove guests, an evening out, days away or a member's absence on one date. Without eventType every entry on the date goes. A day away that is removed can be planned again.
add_food_preferenceRecord that the household, or one member, likes or dislikes an ingredient, a dish, a category, a texture or a way of cooking. Allergies and intolerances are not likes: Bryti keeps them in the app.
delete_food_preferenceRemove a recorded like or dislike, by its subject as get_household_overview shows it.
merge_pantry_foodsMerge two pantry rows the household says are the same food. The first stops being its own row and reads as the second, which keeps its name. The food keys are the ones get_inventory gives. The household can split them again in the app.
upsert_category_frequency_ruleSet how many times a week a meal category should be on the plan, at least and at most. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
upsert_category_excluded_days_ruleSet the weekdays a meal category is never planned. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
upsert_category_on_day_ruleSet that a meal category belongs on a weekday every week, e.g. taco on Fridays. One single date is set_category_for_date. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
upsert_max_cooking_time_ruleSet the most minutes of active cooking a dinner may take, every day or on the weekdays named. One single date is set_max_cooking_time_for_date; the time until dinner is on the table, oven included, is upsert_max_total_time_rule. A rule about the same thing is changed, not added…
upsert_max_total_time_ruleSet the most minutes from the first step until dinner is on the table, oven and resting included, every day or on the weekdays named. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
upsert_price_class_ruleSet how dear dinners may be, every day or on the weekdays named: Cheap, or CheapOrMid. Bryti prices each dinner from store prices; there is no amount in kroner. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
upsert_repeat_after_days_ruleSet how many days must pass before the same dish comes back, 3 to 30. Bryti's default is 10. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.
update_household_settingsChange the household's name, time zone, usual dinner time, address (which decides the stores nearby) or how the week is planned. Only the fields given change. One evening's dinner time is set_dinner_time.
set_household_languageSet the language Bryti uses with the household: nb (Norwegian Bokmål), nn (Nynorsk) or en (English).
select_storesSet the stores the household shops at. This replaces the whole selection, so name every store they want; get_stores shows the ones chosen now. Bryti looks the names up near the household's address, and a name it does not find fails with the stores nearby.
activate_planMake the plan for the week that holds weekStart the one that counts. A plan is live as soon as it is made, so this matters only when the household asks for it.
Details
| Endpoint | https://api.bryti.app/mcp (Streamable HTTP) |
| First published | 6 Nov 2026 |
| Last updated | 6 Nov 2026 |
| Registry name | app.bryti/bryti |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.