Full read-write Claude connector for Toast
Have Claude toggle item availability and pull reporting in Toast
Stop clicking through the Toast back office to 86 an item. Claude toggles item and modifier stock through the Stock API and pulls sales and labor reporting right where your restaurant data already lives, with the guest-facing changes waiting on your approval.
Toast is a restaurant point-of-sale and management platform that runs ordering, menus, payments, and reporting for many restaurants. Teams want Claude to do more than read sales numbers: to toggle item availability, look up menu and labor data, and act inside the system their floor runs on.
What is a Toast MCP server?
A Toast MCP server is a small hosted service that exposes Toast's data and actions to Claude over the Model Context Protocol, so Claude can industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Toast's current connector do today?
Today, Toast exposes partner APIs for orders, menus, labor, and reporting, but access depends on partner approval and the scopes your account is granted, and there is no general-purpose Claude connector. A custom Toast connector can add read and approved write actions, scoped to what your account already permits.
What does full read-write Toast access unlock?
Read-write Toast access lets Claude toggle items and modifiers in or out of stock through the Stock API, look up menu configuration, and pull sales and labor reporting on request. The stock toggles and reporting that used to mean clicking through the back office happen where your restaurant data already lives.
- Look up a menu item's name, description, or price
- Mark an item or modifier as out of stock, then back in
- Set a stock quantity for an existing item via the Stock API
- Pull a sales summary or labor report for a date range
- Toggle item stock status across locations after you approve it
Can Claude look up menu items and pricing in Toast?
Looking up menu items and pricing in Toast is what the connector enables. Claude can read an item's name, description, price, and modifier groups through the Menus API, scoped to the locations your account permits. Menu and pricing edits are made in Toast Web and published, since the Toast API does not support editing those fields.
Can Claude mark an item out of stock in Toast?
Marking an item or modifier out of stock in Toast, then back in, is a write action Claude can prepare for you. Because 86ing an item changes what guests see, it runs as a gated step that applies only after your confirmation, so nothing on the menu flips without you deciding it should.
Can Claude pull a sales or labor report from Toast?
Pulling a sales summary or labor report from Toast for a date range is a read action Claude handles on request. It queries the reporting API within the scopes your account is granted and never sees more of your restaurant data than you already do, so reporting stays limited to the locations you approve.
How a Toast connector works
We build a small MCP server that authenticates to Toast through its partner API with the narrowest scopes the work needs. Read tools (reporting, menu lookups) and write tools (stock status changes) are separated, and changes that affect what guests see are gated behind your confirmation. Claude never gets more access than your own Toast account already has, and we can add IP allowlisting where your setup supports it.
Frequently asked questions
Can Claude change stock on our Toast menu, not just read sales?
Will Claude change prices or 86 an item without my approval?
Does the connector get more access than our Toast account has?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.