For people with an AI assistant

Your kitchen, connected to your 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.

Connect it

  1. Create a token below

    It's shown once. Choose read unless you want your assistant to add things to your pantry for you.

  2. Give your assistant one of these

    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

  3. Ask it something

    "What can I cook tonight?" · "Add two lemons and a bag of spinach to my pantry" · "What's about to go off?"

Your tokens

What a token can and can't do

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.

Meta Muse: say this to it. Muse doesn't have a settings screen for this — you add a service by asking. Meta calls it a Custom Connector, it works for any service that isn't already in their list, and you don't need us to be listed anywhere first. Paste this into Muse, then give it your token when it asks:
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.

MCP is the better door, and here's the honest reason. An API description tells an assistant how to call something. MCP tells it when — each tool carries a description written for the assistant to read, so it knows that "what's for dinner?" means looking in your actual kitchen rather than searching the internet. Same account, same token, same limits either way.

If you'd rather do it by hand

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.

← The Pantry Butler