PantryPilot

Your kitchen, co-piloted. Built for humans and their agents.

● WebMCP: not detected

Pantry inventory

Add what's in your kitchen β€” or ask your agent to do it with add_pantry_items. Items nearing expiry glow red; the agent plans meals to use them first.

This week's dinners

Click πŸ”€ on any day to swap in the next-best recipe β€” humans keep the final call. Agents do the same in bulk via plan_week. "Cooked it" deducts real per-serving portions from your pantry.

Shopping list

Auto-generated from the week plan minus what you already own, consolidated by aisle. Agents fetch it via get_shopping_list or check off items with consume_pantry_items.

Recipe library

A local, offline recipe graph the agent's find_recipes tool searches. Green = you can cook it now.

How PantryPilot uses WebMCP

PantryPilot registers structured tools on document.modelContext so any WebMCP-capable agent (ChatGPT's in-app browser, Chrome with the flag enabled) can drive the app natively β€” no DOM scraping, no guessing.

πŸ”Œ Registered tools

    🧩 The code

    
          

    🀝 Why human + agent?

    Reading a fridge label, deciding "this looks off", tasting, preferring β€” that stays human. Bulk planning, expiry triage, list consolidation, nutritional balance β€” that's agent work. WebMCP is the contract that lets both act on the same state, safely and in structured form.

    Open this page in ChatGPT's in-app browser or Chrome with chrome://flags/#enable-webmcp-testing and try: "Plan my week around what's expiring, then give me a shopping list."