What connecting Claude to your business data looks like
What it is, what you can ask, and what it takes to set up. Toast is our first hosted connection.
Toast keeps a running record of everything happening in your restaurant: every order, every clocked hour, every comp a manager approved. Most of that record sits behind report menus you only open when something has already gone wrong. Connecting Claude to your Toast account turns that same data into something you can ask questions of, in plain language, from your phone or a laptop, without opening a report screen.
What it is
Claude reads your restaurant's own Toast numbers, live, and answers in a sentence instead of a spreadsheet. Under the hood, a small piece of software sits between Claude and Toast's API. It pulls sales, labor, menu, and comp data using credentials you generate yourself and control, and hands Claude only what it needs to answer your question. Nothing gets stored beyond what Toast already keeps. Nothing gets used to train a model. Revoke the connection in Toast at any time and it stops working immediately.
What you can ask
Once it's connected, the kind of question that used to mean logging in and clicking through three reports becomes one sentence. What were sales last week, broken out by day. How labor is running this month against last month. Which items barely sold in the last two weeks. What the comp and void total came to for the week, and who authorized the biggest ones. How this Saturday compares to the Saturday before. Claude pulls the real numbers from your account and answers directly, the same way it would answer any other question. Want a number broken down further, by shift or by day part? Just ask for that too.
What it needs
Two things have to be true first. Your Toast subscription needs to be on Restaurant Management Suite Essentials or higher, the tier where Toast opens up the Standard API access this connection runs on. If you're not sure what tier you're on, your Toast account rep can tell you in one message, or you can check under Toast Web's subscription settings.
Second, you generate your own read-only API credentials directly inside Toast Web, under Integrations, and enter them into the platform yourself. We never see or hold your Toast login. The credentials only allow reading data out, not writing anything back in: no order changes, no refunds, no menu edits. Claude can tell you what happened. It has no way to touch your point-of-sale system.
Where this doesn't reach yet
Worth saying plainly: this is read-only, and it's scoped to your restaurant's own numbers. It won't place orders, issue refunds, or touch loyalty and gift card programs. It won't compare your numbers against other restaurants, because your data stays yours, never pooled or benchmarked against anyone else's. What this does is answer questions about what already happened, fast enough that you ask them instead of letting a report pile up unread.
What it feels like day to day
Most operators use it in short bursts rather than sitting down for a session. A question between tables during a shift. A quick check on Monday before the weekly numbers meeting. A gut check mid-month on whether labor is drifting before the schedule for next week goes out. The point isn't a new routine, it's having the answer available at the moment you want it, instead of waiting until you're back at a computer with Toast open.
Setting it up
The connection lives inside a KJDC membership. Once you're a member, a short setup page walks you through generating the Toast credentials and pasting them in, and a connect tutorial covers the first few questions worth asking. If you would rather not do the Toast Web steps yourself, a done-for-you setup is available too.