Mindful recipes for a good day — docs & privacy policy for the Claude connector
Good Day (GD) exposes 24 tools at https://mcp.gooddayplan.com/mcp. All of them
require you to be signed in. Four read the shared recipe catalog; twenty work on
your own household’s data — profile, pantry, meal plans, grocery lists and
the meals and tasks on your days. No tool can read or change another
household’s data, and no tool takes a user or account identifier as an
argument: who you are comes from your sign-in, never from what is typed.
Access in the tables below means:
| Group | Tool | Title | Access |
|---|---|---|---|
| Catalog | search_recipes |
Search recipes | Read-only |
list_recipes |
List recipes | Read-only | |
view_recipe |
View recipe details | Read-only | |
request_recipe |
Request a missing recipe | Write (adds) | |
| Household | view_profile |
View household profile | Read-only |
set_profile |
Set household profile | Write (changes) | |
| Pantry | view_pantry |
View pantry | Read-only |
add_pantry_items |
Add pantry items | Write (adds) | |
set_pantry_item |
Set pantry item quantity | Write (changes) | |
remove_pantry_items |
Remove pantry items | Write (changes) | |
search_ingredients |
Search ingredients | Read-only | |
cook_now |
What can I cook now | Read-only | |
| Meal plan | get_meal_plan |
Get weekly meal plan | Read-only |
create_meal_plan |
Create a meal plan draft | Write (adds) | |
change_meal_plan |
Update a meal plan slot | Write (changes) | |
finalize_plan |
Finalize plan & build grocery list | Write (changes) | |
view_grocery_list |
View grocery list | Read-only | |
| The day | view_day |
View the day | Read-only |
schedule_meal |
Schedule a meal | Write (adds) | |
add_task |
Add a task | Write (adds) | |
move_event |
Move or unschedule an event | Write (changes) | |
delete_event |
Remove an event from the plan | Write (changes) | |
complete_task |
Complete a task | Write (changes) | |
| Account | delete_my_account |
Delete my account | Write (changes, permanent) |
GD does not contact any outside service on your behalf, with one exception:
delete_my_account also removes your sign-in account at our login provider.
GD’s goal is one dish the whole family eats, so search_recipes and list_recipes show kid-friendly dishes only, by default. The rest of the catalog is hidden, not gone: ask for it and the assistant passes include_hidden. If you are used to the earlier recipe-search version of GD, a search for a spicy dish now returns fewer results.
Searches recipes by natural-language meaning plus structured filters. Use it when you describe what you want in your own words, e.g. “something warm for a cold evening” or “quick chicken and rice dinner”. Category words in the query (“kid friendly breakfast”, “vegan lunch”) are understood as filters.
Parameters (all optional):
| Parameter | Type | Description |
|---|---|---|
query |
string | Natural-language description of the desired recipe. |
meal_type |
string | breakfast, lunch, dinner, or snack. |
type |
string | Diet type: vegan, vegetarian, or non-veg. |
cuisine |
string | Cuisine filter, e.g. indian, italian. |
max_time_min |
integer | Max total time (prep + cook) in minutes. |
min_rating |
number | Minimum rating (0.0–5.0). |
kid_friendly |
boolean | Leave it out: GD shows kid-friendly dishes only by default. false lists the adults-only ones instead. A recipe nobody has judged yet is never returned as either answer. |
include_hidden |
boolean | true lifts the kid-friendly default and shows the whole catalog, including adults-only and not-yet-judged recipes. Use it only when you ask for it. |
max_spice_level |
string | Heat ceiling: none, mild, medium or hot. |
limit |
integer | Max results to return (default 20). |
Returns a ranked list with recipe ID, name, diet type, meal type, cuisine,
total time, rating, kid-friendliness and match score. Results below a minimum
relevance score are omitted — an empty response means the catalog has no real
match (a good moment for request_recipe), not that results were cut off.
Invalid filter values are rejected with a message naming the valid options.
Lists recipes with structured filters and pagination — browsing rather than searching.
Parameters (all optional): meal_type, type, max_time_min,
min_rating, kid_friendly, include_hidden, max_spice_level and limit as above, plus:
| Parameter | Type | Description |
|---|---|---|
source |
string | Filter by source (e.g. admin for curated seeds). |
servings |
integer | Minimum number of servings. |
offset |
integer | Pagination offset. |
Returns one recipe in full: description, ingredients with quantities, ordered steps, prep/cook/total times, servings, rating, and source attribution when present.
Ingredient lines show the food and, after a comma, what to do with it (“onion, diced”). When a dish uses foods that are not on GD’s staples list, a “Not on the staples list” line names them and how many other kid-friendly recipes use each, so you can see what is extra shopping for this dish. It is a flag, not a refusal: you decide.
| Parameter | Type | Description |
|---|---|---|
recipe_id |
integer | Required. The recipe ID from a search or list result. |
Logs a request for a recipe the catalog doesn’t have yet, so a future catalog batch can fill the gap. Nothing is generated on the spot. Repeating an ask bumps its count rather than duplicating it.
| Parameter | Type | Description |
|---|---|---|
query |
string | Required. The ask, e.g. “Korean, quick, no peanuts”. |
meal_type |
string | Optional: breakfast, lunch, dinner, or snack. |
type |
string | Optional diet type. |
cuisine |
string | Optional cuisine. |
exclude |
list of strings | Ingredients or allergens to avoid (recorded with the ask). |
The request is stored with a link to your account; see the privacy policy.
Shows the household’s cooking profile: diet, excluded foods, preferred cuisines, household size, the daily hands-on cooking budget, and any members described individually. No parameters.
Updates the profile. Only the arguments passed change. List arguments are
replaced, not added to — and an empty list means “leave this alone”, so an
allergy list can’t be wiped by accident; emptying a field is done explicitly
with clear.
| Parameter | Type | Description |
|---|---|---|
diet_type |
string | vegetarian or vegan. Omit for no restriction. |
exclude |
list of strings | Foods nobody in the house eats, e.g. ["nuts", "shellfish"]. A hard filter — use it for allergies. |
preferred_cuisines |
list of strings | Cuisines to favour. |
household_size |
integer | How many people eat here; scales quantities. |
daily_active_min |
integer | Minutes a day the household can spend hands-on at the stove (default 45). |
members |
list of objects | The people worth describing individually — see below. |
clear |
list of strings | Fields to empty completely: any of diet_type, exclude, preferred_cuisines, members, daily_active_min. |
Each member has:
| Field | Type | Description |
|---|---|---|
label |
string | Their role at the table: “kid 1”, “toddler”, “grandma”. Not a name, age or birthdate — GD has no field for those and rejects a label that looks like a date. |
spice_tolerance |
string | none, mild, medium or hot (default mild). |
dislikes |
list of strings | Foods or textures they refuse. A preference, not an allergy. |
portion_scale |
number | Appetite relative to an adult (default 1.0). |
picky_eater |
boolean | true if this person refuses a dish outright rather than eating around it. When set, GD only proposes dishes the whole table can eat. |
Lists everything in the household’s pantry with quantities and units. No parameters.
Adds quantities to pantry items by ingredient name, creating entries that aren’t there yet. Never reduces or removes anything.
| Parameter | Type | Description |
|---|---|---|
items |
list of objects | Required. Each with name (string), quantity (number) and unit (string, e.g. lbs, g, pcs). |
Sets one pantry item to an exact quantity, overwriting what was there; creates
the entry if it’s missing. For “how much I have”, where add_pantry_items is
for “how much I bought”.
| Parameter | Type | Description |
|---|---|---|
name |
string | Required. The ingredient name. |
quantity |
number | Required. The exact amount now in the pantry. |
unit |
string | Required. Unit of measurement. |
Removes items from the pantry entirely. Removing something that isn’t there has no effect.
| Parameter | Type | Description |
|---|---|---|
names |
list of strings | Required. Ingredient names to remove. |
Looks up ingredients by name to see what the catalog calls them (“bell peppers” vs “capsicum”). Not needed before adding to the pantry — the pantry tools take names directly.
| Parameter | Type | Description |
|---|---|---|
query |
string | Required. An ingredient name, or part of one. |
limit |
integer | Max results (default 20). |
Lists what can be cooked tonight, ranked by how little is missing from the pantry. Every option already respects the household’s exclusions, dislikes, diet and picky eaters. GD checks whether you have each ingredient, not how much of it, and says so in the response.
| Parameter | Type | Description |
|---|---|---|
meal_type |
string | breakfast, lunch or dinner (default dinner). |
max_missing |
integer | How many missing ingredients still count as “now” (default 3). |
A plan covers one week, Monday to Sunday. It starts as a draft, is filled slot by slot, and is then finalized — which builds the grocery list and puts the meals on their dates.
Returns the current week’s draft plan, with the recipe candidates for the slots still empty, or reports that no draft exists. No parameters.
Creates an empty draft for the current week and returns it with candidate recipes already filtered for the household: excluded foods and disliked foods removed, spice capped, and each dish’s hands-on minutes shown against the daily budget. Fails if a draft already exists for the week. No parameters.
Sets or clears slots in a draft plan — one, several, or a whole week in a single call. Each entry overwrites what that slot held. The batch is all-or-nothing: if any entry is invalid, nothing is written and the error says what is wrong.
| Parameter | Type | Description |
|---|---|---|
plan_id |
integer | Required. The draft plan’s ID. |
slots |
list of objects | Each with day (monday…sunday), meal_type (breakfast, lunch, dinner), recipe_id (the main dish; null clears the slot) and optional sides (list of recipe IDs). |
A slot holds either a whole dish (optionally with one vegetable side), or a
build-a-plate dinner: a protein as recipe_id with its grain and vegetable in
sides. If one part is refused at the table, resend the slot with a different
side and the rest of the dinner stands.
Marks the plan finalized (this cannot be undone), builds its grocery list,
and places every filled slot on its date so view_day can show it.
| Parameter | Type | Description |
|---|---|---|
plan_id |
integer | Required. The draft plan to finalize. |
Shows the shopping list from a finalized plan, grouped by category, with what the pantry already covers listed separately. The list is fixed at finalize time, so it does not shift while you shop.
| Parameter | Type | Description |
|---|---|---|
plan_id |
integer | Optional. A specific plan’s list; omit for the most recent. |
Meals and tasks live on real dates. Each day shows a hands-on total against the household’s daily budget — the minutes someone has to stand at the stove, not the time until dinner is ready.
Days are given as today, tomorrow, a weekday name, or a date like
2026-11-12.
Shows what is on a day: meals, prep, tasks, and the hands-on total.
| Parameter | Type | Description |
|---|---|---|
day |
string | The day to look at (default today). |
days |
integer | How many days from there. 1 (default) gives the full day; more gives one summary line per day. |
Puts a meal on a day — a recipe, or a placeholder with a title.
| Parameter | Type | Description |
|---|---|---|
recipe_id |
integer | The dish. Omit to hold the slot with just a title. |
day |
string | The day (default today). |
meal_slot |
string | breakfast, lunch or dinner (default dinner). |
title |
string | What to call it; defaults to the recipe’s name. |
active_min |
integer | Hands-on minutes, if different from the recipe’s usual. |
notes |
string | Anything for the cook. |
Adds something that has to get done (“thaw the chicken”). A task has no time on the day and does not count against the hands-on budget.
| Parameter | Type | Description |
|---|---|---|
title |
string | Required. What has to happen. |
day |
string | The day it belongs to. Leave empty for a task not tied to a day. |
due_on |
string | A due date, if different from the day. |
Moves something already on a day to another day or meal slot, or takes it off the calendar while keeping it planned.
| Parameter | Type | Description |
|---|---|---|
event_id |
integer | Required. The event, as shown in square brackets by view_day. |
day |
string | Where it moves to. |
meal_slot |
string | A new meal slot, if that changes too. |
active_min |
integer | A new hands-on estimate. |
unschedule |
boolean | true takes it off the calendar but keeps it planned. |
Removes an event entirely. To keep a meal but take it off its day, use
move_event with unschedule instead.
| Parameter | Type | Description |
|---|---|---|
event_id |
integer | Required. The event, as shown by view_day. |
Ticks a task off, or reopens it. The task itself is kept either way.
| Parameter | Type | Description |
|---|---|---|
task_id |
integer | Required. The task, as shown by view_day. |
done |
boolean | true to complete (default), false to reopen. |
Permanently deletes the account and everything stored in it. It works in two steps so nothing is deleted by accident:
| Parameter | Type | Description |
|---|---|---|
confirm |
string | Leave empty to preview. To delete, the exact phrase the preview returned. |
The response states which parts were deleted. Disconnecting the connector does not delete anything; this does. See the privacy policy.