Claude + Toast POS: What Works in 2026
No — there’s no official Claude Toast connector, and this one has a wrinkle most POS integrations don’t. Toast isn’t in Anthropic’s connectors directory, Toast ships no first-party MCP server, and Toast splits API access into reading and writing. For U.S. customers, read-only Standard API access comes with Restaurant Management Suite (RMS) Essentials or higher, and you create the credentials yourself in Toast Web. Writing anything back into Toast is arranged through your Toast account rep. Community “Toast MCP” projects inherit whichever access you hold.
Here’s exactly what’s possible today, where the read/write line sits, and what to use if you want Toast-adjacent work that runs on its own.
Why “just connect Claude to Toast” doesn’t work
Most AI-plus-POS guides get this half right. A restaurant can mint credentials itself: in Toast Web, go to Integrations > Toast API access > Manage credentials and create Standard API credentials (a client ID, a client secret, and the restaurant GUID for each location). For U.S. customers that access is included with RMS Essentials or higher; international and MSA customers pay for it as a separate subscription. What you get is a read-only scope set (orders:read, labor:read, menus:read, stock:read and similar), with OAuth 2.0 client-credentials auth. The moment you want to write back, like pushing a menu change or updating stock, Toast arranges it through your account rep.
That single fact shapes everything about Claude and Toast:
- There’s no directory connector to toggle on.
- There’s no vendor MCP server Toast publishes.
- The community MCP servers on GitHub — for example
BusyBee3333/toast-mcp-2026-complete(~94 tools, local/stdio, write-gated) andmatthewmckenzie/toast-mcp-server— wrap Toast’s REST API but still expect you to supplyTOAST_CLIENT_ID,TOAST_CLIENT_SECRET, andTOAST_RESTAURANT_GUID. No credentials, no connection.
So the honest starting point: if you’re a U.S. restaurant on RMS Essentials or higher, you already have read-only credentials waiting in Toast Web. Anything that writes needs a conversation with your Toast rep first.
What Claude can do around Toast today
If you create Standard API credentials, you can point a community MCP server at Claude Desktop or Claude Code and query menus, orders, or sales inside a chat. It’s read-only unless Toast has granted you write access. It looks like every other Claude MCP setup: useful for pulling data into a conversation you’re actively driving, and you host and maintain the server yourself.
If you’d rather not set up credentials, Claude still helps with the work around Toast without touching the API:
- Paste an exported Toast sales or labor report and ask Claude to summarize it, flag anomalies, or draft a note to your team.
- Have Claude draft vendor emails, staffing messages, or a weekly recap you write from Toast numbers.
- Use Claude to reason about menu changes, pricing, or scheduling based on figures you copy in.
None of that is a live connection — it’s Claude working on data you bring it.
The limits that actually matter
Even with credentials and a community MCP running, the shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- Reading is the default. Standard API access is read-only, so a Claude chat can report on Toast but not change it unless your Toast rep has arranged write access.
- No triggers, no monitoring. MCP tools only run inside a conversation you start. There’s no “when a big order comes in, alert the kitchen lead” or “when nightly sales close, email me the recap.” Nothing fires on a Toast event — you have to be there, prompting.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on restaurant agent.
If you want Toast work that runs on its own: Carly
The moment you want something to happen around Toast without you in the chat — a nightly sales recap emailed to owners, a low-inventory heads-up, a follow-up when a catering order lands — you’ve crossed past what Claude’s MCP setup is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud — a nightly recap, a Monday-morning labor summary, a reminder when a catering deposit is due; your laptop doesn’t need to be awake.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, and updates your CRM.
- Connects to Toast with your own credentials — Carly connects to thousands of apps. For Toast, create Standard API credentials in Toast Web under Integrations > Toast API access > Manage credentials, then paste the client ID, client secret and restaurant GUID at carlyassistant.com/integrations under Custom API Keys. Carly reads Toast and does the work in your inbox, calendar and books; if your rep turns on write access, Carly uses that too.
- Builds the workflow for you — describe “email owners a sales recap every night after close” in plain English; Carly interviews you, then builds it with you. No prompt engineering.
Free Zapier-style workflows; AI agents from $35/month. Carly connects to thousands of apps; see integrations. For a side-by-side of the options, see the best AI automation tools for Toast.
Claude vs Carly for Toast
| Claude (community MCP) | Carly | |
|---|---|---|
| Needs Toast API credentials | Yes | Yes (for live API); adjacent flows otherwise |
| Read Toast data | Yes, in a chat | Yes, in a chat or on a schedule |
| Acts on triggers / events | No | Yes |
| Sends nightly recaps on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Works from exports / email when no API | Manual paste | Yes (automated) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude’s MCP route is a Toast lookup inside a chat that you host yourself. Carly is a teammate that acts on restaurant events and sends the results where your team already works.
Frequently Asked Questions
Does Claude work with Toast?
Not through an official connector — Toast isn’t in Anthropic’s directory and Toast ships no MCP server. Community MCP servers can connect Claude to Toast’s REST API using credentials you already hold. U.S. restaurants on RMS Essentials or higher can create read-only Standard API credentials in Toast Web; write access is arranged through your Toast account rep.
Can a restaurant self-provision a Toast API key for Claude?
Yes, for reading. For U.S. customers, Standard API access comes with Restaurant Management Suite Essentials or higher; international and MSA customers pay for it as a standalone subscription. You create the credentials yourself in Toast Web under Integrations > Toast API access > Manage credentials, using OAuth 2.0 client-credentials against a read-only scope set. Write access, like pushing a menu change or updating stock, is arranged through your Toast account rep.
Can Claude send my nightly Toast sales recap automatically?
No. Claude’s MCP tools only run inside a conversation you start — there are no event triggers or schedules. For an automatic nightly recap, you need an agent platform like Carly, which fires on schedules and events in the cloud and can send the email itself.
What can Claude do with Toast without API credentials?
Work on data you bring it: paste an exported Toast report and Claude will summarize it, flag outliers, or draft messages. It’s not a live connection, but it’s genuinely useful for the reasoning-and-writing part around your Toast numbers.
More: Best AI automation tools for Toast · Claude connectors · Claude + Square · Claude + Shopify · Can Claude send emails · Claude vs Carly · Best AI tools for solopreneurs
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
