ChatGPT Plugin

Pantry Persona

Meal plans, recipes, grocery

Brand: Pantry Persona

Category: Consumer & Lifestyle
Primary Subcategory: Recipe & Cooking Assistants

Integration details

Description

Your kitchen inside ChatGPT: recipes, a weekly meal plan, and a grocery list built from what's already at home. Pantry Persona remembers what's in your fridge, what your family can and can't eat, and which brands you prefer, then keeps everything in sync as you cook and shop through the week. Meal plans: Generate a full week of meals in one ask, or build it day by day. Plans respect your household's food preferences and eating rules automatically and carry per-meal nutrition. Recipes: Save a recipe from a website, a cooking video, or a social post, or create one in conversation. Search by ingredient, cuisine, or what you can make right now with what's on hand, and group favorites into collections. Shopping lists: Visual, interactive lists organized by store. Ask for one from your meal plan and it skips anything already in your pantry; check items off with one tap and send it to Instacart when you're ready to buy. Cook Mode: Start cooking a recipe and get step-by-step guidance. When you're done, ingredients are deducted from your pantry and leftovers are tracked with expiration dates. Household: Profiles store each family member's food preferences, eating rules, favorite brands, and nutrition targets, and every suggestion, plan, and search filters through them. Invite family members and everyone works from the same pantry, recipes, and shopping lists in real time. Nutrition: See calories and macros on every recipe and meal, set daily targets for each person, and check how today or the week is stacking up. Log what you actually ate, even a meal out, and it counts toward your totals. Receipts and staples: Pantry Persona tracks expiration dates, predicts when you'll run low on staples, and learns the brands and prices you buy. Grocery receipts become an up-to-date inventory and a clear picture of your spending. A guided setup gets a new kitchen planned and shopped in a few questions.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Consumer & Lifestyle
Primary Subcategory: Recipe & Cooking Assistants
Secondary Subcategories: None listed
Brand: Pantry Persona
Access: Account required
First tracked: 2026-07-11
Tool count: 22
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Recipe & Cooking Assistants

View Category

Listed in alphabetical order

Primary Subcategory

1-2-3-Cook+Bake Food to eat!Coming soonGet notified

AcikMutfakComing soonGet notified

Aftensmad i dagComing soonGet notified

ask.recipesComing soonGet notified

BarbaroComing soonGet notified

Pantry PersonaComing soonGet notified

Tools

22 tools agents can invoke

Use this when the user wants recipe ideas, asks what to make/cook ("what's for dinner", "what can I make with X"), or asks for recipes by name, ingredient, tag, or diet (keto/vegan/low-carb/paleo — pass forDiet so diet results are grounded in saved data, not guessed). Prefer their saved recipes over generic ideas. Pass excludeRecipeIds when rejected. Returns data only. If they ask what's already scheduled ("what's for dinner tonight"), call show_meal_plan instead.
find_recipes
Use this when the user asks "how much do I spend", "what brands do I buy", "when will I run out of X", "how am I doing this week", "am I hitting my target", or "what nutrients am I low on". Returns analytics — spending, price history, brands, shopping patterns, restock predictions, consumption, receipts, weekly nutrition trends, hit rate, top deficits — no widget. Not for recipe or pantry lookups (→ find_recipes, get_pantry) or today's intake totals (→ get_user_context).
get_insights
Use this when the user says hello, asks about their household, asks about nutrition intake today ("what's my sodium today"), or starts a meal-planning session that needs the full kitchen snapshot upfront. Returns dietary profiles, pantry highlights, expiring items, today's meal plan with logged/target nutrition totals, shopping status, staple tracking, and saved planning workflow. Do not use for specific recipe-discovery prompts ("dinner ideas", "what should I cook") — call find_recipes. Not for weather or general knowledge.
get_user_context
Use this when the model needs ingredient data internally — to match pantry contents against a recipe, check availability before suggesting meals, or reason over inventory before answering. Returns the pantry as data for the model; no widget. Do not use when the user asks about their own pantry ("what's in my pantry", "what's expiring", "do I have X") — call show_pantry. Not for "running low"/restock (→ get_insights) or "what should I do next" (→ get_next_steps).
get_pantry
Use this when the user asks what to do next or seems unsure how to use the app — "what should I do next", "what's next in my kitchen", "what can I do", "what features haven't I tried", "help me get started". "My kitchen" means their Pantry Persona kitchen, not a physical room. Returns 2-3 personalized next-step suggestions across profiles, pantry, recipes, shopping, meal plan, and receipts. Do not use when the user has a specific action in mind.
get_next_steps
Use this when the user opens the Kitchen tab in a thread. Shows tonight's dinner and this week's kitchen counts. Not for single-area questions; the matching show tool covers those.
kitchen_thread
Use this when the user reports eating a meal — a recipe they cooked ("I made the chicken pasta", "just cooked dinner") or an ad-hoc/restaurant meal given by its macros with no recipe ("ate out, 800 cal 50g protein"). Logs it toward nutrition; a recipe also deducts pantry and updates cook history. Do not use for browsing or planning meals — call find_recipes.
post_cook
Use this when the user puts a recipe into a named group — "add to Ben Approved", "throw this into favorites", "create a weeknight dinners collection" — removes one, or lists them ("pull up collections"). Creates, renames, deletes, lists, and edits collection membership. Auto-creates the collection if missing. Do not use for likes or dislikes — call manage_profiles — or to save a recipe — call manage_recipes.
manage_collections
Use this when the user names a recipe for a day, or asks to replace, swap, or change a planned meal, e.g. "replace Wednesday dinner with a salmon recipe"; freeform meal names work without recipeIds. One-meal or guest dietary scopes ("Mark is vegetarian Saturday") belong here, not manage_profiles. Commits one day at a time: set assigns, clear removes, move relocates; never set_week for bulk. Preview, then re-call with the confirmationToken; never narrate a meal change without that completed call.
manage_meal_plan
Use this when the user corrects their pantry inventory ("I don't have X anymore", "we used the Y", "add these groceries"), or reports cooked leftovers. Adds, removes, updates, or consumes pantry items, logs leftovers, clears expired items, and recategorizes miscategorized items. Handles batches of up to 100 items per call. Do not use this for shopping list changes — call manage_shopping instead — or to display the current pantry — call show_pantry.
manage_pantry
Use this when the user names a product preference ("I prefer [brand]", "forget my preference", "what are my brand preferences") or sets a behavioral preference about how you respond ("give me one at a time", "step at a time", "too much info", "stop reminding me about everyone's allergies", "don't show that recipe again" — pacing, info density, decision style, dietary acknowledgement, recipe exclusions). Do not use for household dietary profiles (call manage_profiles) or recipe-level preferences (call manage_recipes).
manage_preferences
Use this when the user states a standing dietary exclusion/allergy ("always avoid mushrooms", "never cilantro" — save it, don't just acknowledge), or makes a permanent profile change, saves a planning workflow, sets/clears a nutrition target ("set my daily calorie target to 2000", "Ben's target is 2000 calories"), saves threshold filters ("sodium under 800mg"), self-identifies ("I'm Kevin"), or deletes a profile. Manages diets, likes/dislikes, per-person targets/thresholds. Not for one-meal scopes (→ manage_meal_plan), brand preferences (→ manage_preferences), or display (→ show_profiles).
manage_profiles
Use this when the user pastes a recipe URL (save_urls), pastes recipe text or a photo (save), edits a recipe, rates it, generates a share link, buys one recipe's ingredients on Instacart (shop), previews a swap without saving ("substitute beans for lentils", "what if I use almond milk", substitute), persists that swap as a recipe (save_as_variant), or wants threshold-filtering ("over 800mg sodium", audit). Do not use to browse, search, or display — call find_recipes or show_recipes; whole-list export is manage_shopping.
manage_recipes
Use this when the user adds to their shopping list, marks items bought, clears items, sets up staples, or exports the WHOLE saved list to Instacart. Named stores ("Costco", "Aldi", "H-E-B") are the user's in-app Pantry Persona lists, not third-party retailer carts — act here: pass storeName, never default to first store. move_item relocates items between stores. Do not use for pantry — call manage_pantry — or to display — call show_shopping. For one recipe's ingredients, call manage_recipes shop.
manage_shopping
Use this when the user opens Pantry Persona from the sidebar. Shows tonight's dinner and this week's kitchen counts. Not for single-area questions; the matching show tool covers those.
kitchen_home
Use this when the user uploads a receipt image, types receipt items like "milk 3.99, eggs 4.50", or pastes receipt text. Adds items to the pantry in one call — dedupes, classifies, estimates expiration, records prices, auto-checks matching shopping items, and clears items already checked off from a prior trip. Do not use for individual pantry adds — call manage_pantry.
process_receipt
Use this when the user says "shop for my meals", "what do I need to buy for this week", or right after committing a new meal plan. Generates a shopping list from the saved meal plan — checks what's in the pantry and adds what's missing. Do not use for individual shopping items — call manage_shopping.
shop_for_meal_plan
Use this when the user asks about household members, dietary preferences, allergies, eating rules, "who can eat what", or right after manage_profiles mutates a profile. Displays household food profiles — diets, exclusions, likes, dislikes, and dietary goals for each member — as an interactive widget. Do not use this to create or edit profiles — call manage_profiles with the appropriate action instead.
show_profiles
Use this when the user asks about planned meals, what's on the schedule, what's for a specific slot today/tonight/tomorrow ("what's for dinner tonight"), or right after manage_meal_plan mutates the plan. Displays the weekly meal plan as a calendar widget with today's meal highlighted and unconfirmed past meals surfaced. If the requested slot is empty, chain to find_recipes with matching timeOfDay. Do not use this to edit the plan — call manage_meal_plan instead.
show_meal_plan
Use this when the user asks about their pantry — "what's in my pantry", "what's expiring", "do I have X", "show me what I have" — or right after a pantry mutation. Displays the pantry as an interactive widget, grouped by category with expiration tracking. Do not use when the model needs raw ingredient data internally — call get_pantry. Not for "running low"/restock (→ get_insights) or "what's next in my kitchen" (→ get_next_steps).
show_pantry
Use this when the user asks to see, browse, or look at recipes ("show me my recipes", "what recipes do I have"), or right after find_recipes returns results that should be displayed. Renders the recipe widget — accepts recipeIds for a specific subset, or query/tags to filter, or no parameters to show the full collection. Do not use for data reasoning that does not need a visible widget — call find_recipes instead.
show_recipes
Use this when the user asks about their shopping list, says "going shopping", "heading to [store]", "what do I need", or "export my list", or right after manage_shopping mutates items. Displays the shopping list as an interactive widget, grouped by store and aisle order when available. Do not use this to add, check, or remove items — call manage_shopping with the appropriate action instead.
show_shopping

FAQs

Pantry Persona ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Pantry Persona's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Pantry Persona alternatives on ChatGPT?

As of 2026-11-02, Pantry Persona competes with 1-2-3-Cook+Bake Food to eat!, AcikMutfak, Aftensmad i dag, ask.recipes, Barbaro, Bite Recipes, Boy or Girl Names, Braai BBQ Planner and 34 more in ChatGPT Recipe & Cooking Assistants, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.