I connected Claude to my Toast POS.

Your inbox is full. Slack is piling up. Client messages need a response yesterday. Typing thoughtful replies to all of it takes hours you don't have.

Wispr Flow turns your voice into clean, professional text you can send the moment you stop talking. Speak like you would to a colleague — tangents and all — and get polished output. Emails, Slack, LinkedIn, WhatsApp, whatever's open.

89% of messages sent with zero edits. Used by teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, and iPhone.

Try Wispr Flow free

Sunday morning I opened Claude and asked my phone what the bar did last night. Four seconds later: net sales, 352 checks, a $33 average, tips. Straight from my Toast.

The Toast app can show me most of that too. Here's the part that matters: I kept asking it things. Things the app couldn't do. Compare the last four Saturdays, hour by hour, and tell me which hour is growing and which is dying. Show me every time entry this week that's missing a clock-out. Saturday's labor as a percent of sales, for both stores, and how much of it was overtime. It answered all of it, in plain English, while I poured coffee.

I love the Toast app. It was a miracle when it came out, and it's still pretty restricted. This opens the gates quite a bit.

If you've used ChatGPT or Claude for your restaurant, you know the routine. You want help reading your numbers, so you go into Toast, run a report, download it, upload the file into the chat, and ask your question. Next week, same thing. New report, new download, new upload. Every question starts with ten minutes of homework.

I built tools this way for a year. My labor tool ran on me feeding it sales and labor exports by hand, every week. Soon enough I connected my Chrome browser to Claude so it could go get things a little more directly. The problem: browser connections can be unreliable. If you're logged out when a scheduled task fires, it just doesn't run. A tool that works 80% of the time is worse than doing the job yourself.

What I built this weekend removes all of that. Claude is now connected directly to my Toast. It can see my sales, my labor, my time entries, my product mix. Live, any moment, from my phone. When I ask a question, it goes and looks. The homework step is gone. Forever.

Think of it like this: Claude used to be a brilliant consultant you had to mail copies of your books to. Now the consultant has a key to the office.

And answering questions is the smaller half. The real prize is what this makes buildable. This morning, hours before this connection existed, I finished a labor budgeting tool that ran on operators downloading their own Toast exports and feeding them in by hand. Caveman, and it was still the most dependable option there was. I hadn't even published it before the pipe made it obsolete. I'll publish it anyway, with a note, and the rebuilt version will run on the pipe. Because now the tools pull the data themselves: a scheduled report that checks every location before I wake up. A labor auditor that grabs the week's punches on its own, every Monday, without fail. Real agents, running on real numbers, on a schedule. As far as I can tell, a dependable pipe between Toast and AI has never existed before this one. Building your own tools just got about a thousand times easier.

Toast has a doorway for this: an API, which is restaurant-tech for "a way for other software to talk to your POS." Most operators have never heard of it because Toast doesn't advertise it. You have to ask for it, by name.

Somebody had already published a free tool on GitHub that claimed to connect AI to Toast through that doorway. I had Claude inspect it for safety and wired it up. Every single call failed. Turns out the tool had never worked. Once. For anyone. One buried line read Toast's answers wrong, and nobody had ever noticed, because nobody had ever run it against a real restaurant.

So Claude and I fixed it. Seven bugs, tested against my own stores, checked against numbers I know by heart. Then we put it on a $5-a-month server, locked it with a password, and plugged it into Claude. The whole thing took a weekend.

The access alone has me excited. There's information in my Toast I was never able to see on the app, and now it's one question away, from anywhere. And the thing that blows the doors off everything: there's now a wide-open path to genuine agents. The tools I've built in-house for labor budgets, punch audits, and daily reports can now pull their own data and run themselves, on schedule, reliably. That's the game.

An operator seeing their numbers a day sooner, every day, makes better calls all year. That's the entire pitch.

I published the fixed code free, and I wrote down every click it takes to build yours. The exact request that gets you API access from Toast, every screen spelled out, the ten-minute server setup, the moment you connect Claude and ask your first question. If you can follow a recipe, you can do this. Restaurant people figure things out.

And before anybody asks: yes, this should work with ChatGPT too. The connection is built on an open standard called MCP, and ChatGPT, Cursor, and most of the other AI tools now speak it. You build the pipe once and every one of them can drink from it. I built and tested mine with Claude, so that's the path I can vouch for.

Here's the whole thing:

Toast was first because that's what I use. The other systems are coming.