Toast MCP Server

Toast

Restaurant reporting for groups running on Toast. Answer operational questions about sales, labor, individual checks, menu mix, and card payouts across one or many locations — without exporting spreadsheets from Toast Web.

Start here

1. See your locations — list every site in the connected group when you need names or ids for filtering.
2. Queue the report you need — sales summary, check detail, labor, menu mix, or payout. Each request returns an id.
3. Fetch the finished report — use that id a few seconds later. Retry the fetch if the rows are not ready yet.

Leave location filters empty to include the whole group. Pass specific location ids when the question is about one restaurant.

What you can answer

Sales summaries can also break down by revenue center, dining option, or order source when the user asks for that split.

Dates

Business dates are eight-digit calendar days (20260706 = 6 July 2026). When no date is given, single-day reports default to yesterday. Match the window to the question — one day for a daily pulse, up to seven days for a week, up to 31 for a month. Check and payout reports are single-day only.

What is not available yet

Changing menus, placing orders, editing employees, or reading live open checks needs broader Toast permissions than a standard reporting connection provides. If the upstream response says access is not permitted, explain that limitation and stay on the reporting flows above.

Async reports

Every report is queue then fetch. Do not treat an empty first fetch as "no data" — wait briefly and fetch again with the same id.

Menu mix reports default to MENU_ITEM grouping so rows name individual sold items (cocktails, wine, burgers, etc.). Location-only totals appear when no item grouping is used — that is not the usual menu-mix question. Item grouping works on day or week windows only.