For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://www.pantrypersona.com/api/mcp
Skill page: https://www.mcpbundles.com/skills/pantry-persona-mcp
Publisher MCP server
Tools: 20
MCP App
Live probe refreshed Nov 16, 2026 · Endpoint host www.pantrypersona.com
Explore capabilities (20)
read 10
write 10
Manage
7
Show
5
Get
4
Other capabilities
4
Manage shopping list
write
manage_shopping
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
Description may be truncated on the public preview.
This server may ask you to sign in when your AI client connects.
Maintain this listing
Operate Pantry Persona? You can take over the listing's metadata.
Operate Pantry Persona?
Take over this listing's metadata — name, description, category, logo, website, contact email, and skill content. Verification is a 6-digit code we email to one of the maintainer addresses your server already publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
OAuth sign-in
API key
MCP App
Pantry Persona
Connect your account, then chat with AI to run tools.
AI meal planning assistant with kitchen memory. Tracks pantry inventory, dietary restrictions, and family preferences to generate personalized meal plans and grocery lists.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Manage shopping list — 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 pantry inventory — 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 meal plan — 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.
Find recipes — 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.
Get pantry data — 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).
Frequently Asked Questions
What is the Pantry Persona MCP server?
AI meal planning assistant with kitchen memory. Tracks pantry inventory, dietary restrictions, and family preferences to generate personalized meal plans and grocery lists. It provides MCP tools that your client discovers when it connects (this page may not list every tool name) that AI agents can use through the Model Context Protocol (MCP).
How do I connect Pantry Persona to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/pantry-persona-mcp. Authentication is handled automatically.
Remote MCP directoryUnlimited tool calls through MCPBundlesThe operator of this MCP may charge for API usage, seats, or OAuth access. Check their site before heavy use.
Manage recipes — 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 e
Shop for meal plan — 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.
Log cooked recipe — 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.
Process receipt — 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.
Get insights — 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).
Manage profiles — 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 scop
Manage collections — 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 preferences — 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
Get kitchen snapshot — 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 (Pro), 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. N
Show shopping list — 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 pantry — 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 recipes — 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 meal plan — 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 household profiles — 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.
Get personalized next steps — 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.
Pantry Persona is a remote MCP server. The live tool list is supplied by the server when your MCP client connects, so the count is not fixed on this public page. After you connect in MCPBundles Studio or your client, you will see the tools your session can call.
What authentication does Pantry Persona require?
Pantry Persona uses One-click sign in or API Key. Pantry Persona requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.