Toast MCP Server
The Toast MCP server lets AI agents read sales, order, menu, and labor data from Toast and act on it. Connect Toast to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Toast doesn't ship an MCP server.
What is the Toast MCP server?
The Toast MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read order, sales, menu, and labor data from Toast and take actions against it through a standard protocol.
In short: Toast is the cloud restaurant platform behind point-of-sale, online ordering, payroll, and operations for over 100,000 restaurants, especially fast-casual and full-service.
Toast doesn't ship an official MCP server, and Toast offers partner APIs, but they don't expose everything visible in the Toast dashboard, and the richest operational data lives in Toast's mobile apps. Supergood builds and maintains the connector by reverse-engineering Toast's authenticated mobile and web APIs and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.
What you can do with Toast via MCP
Once connected, an agent can:
- Pull real-time sales and check data by location, day, or daypart.
- Look up menu items, modifiers, and pricing across one or many restaurants.
- Retrieve order detail (line items, payments, discounts, voids) for reconciliation or reporting.
- Get labor data: shifts, hours, and timesheet entries.
- List locations and roll metrics up across a multi-restaurant group.
- Surface payment and tender breakdowns for daily close.
How to connect Toast to Claude, ChatGPT & Cursor
Connecting works like any other MCP server. The short version:
- Claude (Desktop or claude.ai): add the Toast MCP server under Settings → Connectors (or your MCP config), authorize the Toast account Supergood provisions, and the tools show up in any chat, including agent runs.
- ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the Toast tools in conversations and in agent mode.
- Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.
Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.
How Supergood builds the Toast MCP server
Supergood doesn't wait for Toast to ship an API. We reverse-engineer the authenticated mobile and web APIs behind Toast, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.
- Auth and MFA, handled. Supergood provisions a dedicated Toast account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
- Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape Toast's front-end happens to return.
- Monitored and adapted. When Toast changes its mobile and web UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
- Mobile-grade data. Toast's mobile apps expose operational detail the web APIs don't. Supergood works at the network level to bring that through.
Getting Started
- Schedule Integration Assessment
Book a 30-minute call to confirm which Toast modules and workflows you need and how authentication should work.
- Supergood Builds and Validates Your MCP Server
We deliver a hardened Toast connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Toast changes.
Use Cases
Daily close, automated
- Pull each location's sales, payments, and tender breakdown after service - Reconcile against the bank deposit and flag mismatches - Draft the daily summary for the operator
Multi-location reporting
- Roll sales, labor cost, and item mix up across every restaurant in the group - Compare dayparts and locations on demand - Feed a dashboard or a weekly recap without manual exports
Menu and pricing audits
- Compare menu items and prices across locations to catch drift - Verify a price change rolled out everywhere - Pull modifier configurations for a new-location setup
Labor and operations
- Surface shifts and hours for payroll review - Flag overtime or understaffed dayparts - Pull order-level detail to investigate refunds or comps
Technical Specifications
MCP transport
Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.
Authentication
Supergood provisions a dedicated Toast account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.
Supported clients
Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.
Tools exposed
7 tools covering the workflows listed above; the set is scoped to the modules you license.
Data freshness
Near real-time reads against Toast's live system; not a nightly export.
Rate limits
Tuned to Toast's tolerances; Supergood paces requests to avoid tripping security throttles.
Latency
Sub-second for most reads under normal load; writes reflect the underlying platform timing.
Session management
Automatic re-auth plus cookie/token rotation, with health checks.
Security
Encrypted transport, scoped access, and audit logging; respects Toast role-based permissions.
Webhooks
Optional asynchronous delivery for long-running operations; polling otherwise.
Reliability
Retry logic, backoff, and idempotency keys to avoid duplicates.
Adaptation
Continuous monitoring for Toast mobile and web surfaces changes, with rapid connector updates.
Frequently asked questions
No. Toast doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Toast's authenticated flows and exposing them as MCP tools, plus the underlying REST API.
All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.
Supergood provisions a dedicated Toast account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.
Yes. Reads and writes hit Toast's live system, not a nightly export. Toast offers partner APIs, but they don't expose everything visible in the Toast dashboard, and the richest operational data lives in Toast's mobile apps.
Both. The MCP tools are a layer on top of a normalized REST API for Toast; you can call either, from an agent or from your own code.