Connect Toast to Claude Code

Have Claude toggle item availability and pull reporting in Toast. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Toast to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Toast, you add a Toast MCP server: a small hosted service that exposes Toast's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Toast account. No API keys pasted into config files.

claude mcp add --transport http toast https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Toast once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Toast access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Toast API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Toast changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Toast connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Toast connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Toast account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Toast's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Toast?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Toast account it signs in with. Revoking access is one click in Toast.

More on the Toast connector

Toast connector for claude.ai Square + Claude Code Stripe + Claude Code QuickBooks Online + Claude Code

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.

Build my connector Talk to us