For people with an AI assistant
Every other recipe app can tell an assistant what recipes exist on the internet. The Pantry Butler can tell it what's in your kitchen — so it can answer the question that actually matters at six o'clock.
"What can I make for dinner tonight?"
Chipotle Steak Bowl — you have all eight ingredients.
Marry Me Chicken — everything but the sun-dried tomatoes.
Use the spinach first, it's three days old.
That answer isn't a search. It's your own saved recipes, scored against the things actually in your cupboard and fridge. No other integration can produce it, because no other service knows what you have.
It's shown once. Choose read unless you want your assistant to add things to your pantry for you.
If it speaks MCP — Claude and ChatGPT do — use:
https://thepantrybutler.com/mcp
Otherwise point it at the API description and it
will work the rest out. This is the one to give Meta Muse:
https://thepantrybutler.com/openapi.json
"What can I cook tonight?" · "Add two lemons and a bag of spinach to my pantry" · "What's about to go off?"
Sign in to create a token.
Sign inCopy this now — it's stored only as a hash and can't be shown again.
| Name | Scope | Last used |
|---|
No tokens yet.
A token reaches your recipes and your pantry, and nothing else. It cannot see or change your subscription, alter your account settings, delete your account, or read your email address. If one ever leaks, revoke it here — the worst case is that someone sees a list of recipes.
Build a custom integration to The Pantry Butler. Its OpenAPI document is https://thepantrybutler.com/openapi.json and it authenticates with a bearer token.
Two things worth knowing. Meta says plainly that it doesn't review custom connectors — so they ask you to read the privacy policy of whatever you connect, and ours is here. And we are not a listed connector in Meta's directory, which is a badge, not a requirement; the connector above works the same either way.
curl https://thepantrybutler.com/api/v1/cook-tonight \
-H "Authorization: Bearer pb_live_..."
Or over MCP — streamable HTTP, JSON-RPC, same token:
curl https://thepantrybutler.com/mcp \
-H "Authorization: Bearer pb_live_..." \
-H "content-type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Full endpoint list and limits are on the API page.
Yes. The Pantry Butler runs an MCP server at https://thepantrybutler.com/mcp, published in the official MCP registry as com.thepantrybutler/pantry. You create a token on this page, give your assistant the endpoint, and it can then answer from your own saved recipes and the actual contents of your pantry — not from a web search. Assistants that do not speak MCP can use the OpenAPI description at https://thepantrybutler.com/openapi.json instead.
The Pantry Butler. The endpoint is https://thepantrybutler.com/mcp (streamable HTTP, JSON-RPC), also served at /.well-known/mcp, and it is listed in the official MCP registry as com.thepantrybutler/pantry. It exposes your saved recipes and your pantry, so an assistant can answer “what can I cook tonight” for you specifically.
Ask what you can cook tonight from what you already have, add or remove pantry items, check what is about to go off, and read the recipes you have saved. A read-only token can do the first and the last; a read-write token can change your pantry.
A token reaches your recipes and your pantry and nothing else. It cannot see or change your subscription, alter account settings, delete your account, or read your email address. Tokens are shown once, stored only as a hash, and can be revoked on this page at any time.
No. Connecting is included on the free plan, which keeps 20 recipes. Premium removes the recipe limit; it does not gate the assistant connection.