Skip to main content
Glama

Toast MCP

CI npm license

A Model Context Protocol server that connects Claude to the diner side of Toast. It finds restaurants that take orders through Toast and reads their menus, and, when you are signed in to toast.app, reads your own order history, loyalty programs and Toast Cash.

WARNING

AI-developed project. Claude Code built this codebase and maintains it, and no human has audited the implementation. Review the code and tool permissions before you use it.

What you can do

  • "Which restaurants near me can I order takeout from on Toast right now?"

  • "What's on the menu at https://order.toasttab.com/online/…? Anything vegetarian under $12?"

  • "Is the oat-milk latte at that café out of stock today?"

  • "Compare the online menu with the full in-store menu."

  • "What did I order from that Thai place last week, and what did it cost?"

  • "How close am I to a reward at my coffee shop? What's my Toast Cash balance?"

Related MCP server: OurFamilyWizard MCP

How it works

Toast's diner-facing sites (order.toasttab.com) and its ordering GraphQL gateway (ws-api.toasttab.com/do-federated-gateway) sit behind Cloudflare. Cloudflare refuses server-side clients: it serves a challenge page, or the gateway answers {"errors":[{"message":"Forbidden"}]}. This server therefore makes no direct requests. Every call goes through your own browser via the ContextMint Bridge extension, using @fetchproxy/server on 127.0.0.1:37149. You pass any "verify you are human" check yourself, in your own tab. Nothing is bypassed.

Tools

Tool

What it does

toast_find_restaurants

Restaurants near a latitude/longitude that are open for takeout (or delivery) at a given time, nearest first. Each result includes its GUID, shortUrl, ordering link, address and distance.

toast_resolve_restaurant

Turns a Toast link, shortUrl or GUID into the restaurant GUID that toast_get_menu needs.

toast_get_menu

Reads the online-ordering menu, the full register (POS) menu, or both merged. Supports search, out-of-stock filtering and a limit.

toast_list_orders

Your order history, newest first: restaurant, time, dining option, status, items and total. Pages with next_page_token.

toast_get_order

One past order as a receipt: items with modifiers, subtotal, tax, tip, service charges, payments and delivery details.

toast_get_loyalty

Your restaurant loyalty programs: balances and progress toward the next reward.

toast_get_wallet

Your Toast Cash: balance, next expiry, expiring units and received units (gifts name the sender).

toast_graphql

Runs a read-only GraphQL query against the gateway, for exploring data the other tools don't cover. Mutations are refused.

toast_healthcheck

Round-trips the bridge and gateway, and names the hop that failed.

All of these tools are read-only. None of them places an order, touches a cart, redeems a reward or changes your account. The four account tools (toast_list_orders, toast_get_order, toast_get_loyalty, toast_get_wallet) work only while you are signed in to toast.app in the bridged browser.

What is verified and what isn't

The operations behind the dedicated tools (nearbyRestaurants, menusV3 and restaurantV2ByShortUrl) were live-verified on 2026-10-24 through a bridged browser. Menu prices are in dollars, and both TAKE_OUT and DELIVERY work. The gateway only answers requests that carry a guest session, which the server mints itself from an order.toasttab.com page through your browser, so you don't need to do anything beyond keeping that tab open.

The account tools run Toast's own guest-app queries (copied verbatim from toast.app's bundle), and every shape they parse was captured live and kept, scrubbed, as a test fixture. They authenticate with your toast.app access token, which the bridge reads from that one cookie for each call. The server never refreshes the token (refreshing rotates it and would sign your browser out), so if it has lapsed you'll be asked to reload toast.app. Saved payment methods and the account profile are deliberately not exposed.

Install

  1. Install the ContextMint Bridge extension from its releases page. Chrome takes the unpacked zip.

  2. Open any restaurant's ordering page on https://order.toasttab.com and leave the tab open. It relays the API calls. For the account tools, also keep a signed-in https://toast.app tab open.

  3. Add the server to your MCP client:

{
  "mcpServers": {
    "toast": { "command": "npx", "args": ["-y", "toasttab-mcp"] }
  }
}

Node 22 or later is required. No credentials are configured here. On first run, the extension asks you to approve the pairing. It lists toasttab.com and toast.app, and a read of the toast-customer-access cookie for the account tools.

Configuration (all optional)

Variable

Default

Purpose

TOAST_WS_PORT

37149

Bridge WebSocket port

FETCHPROXY_WS_HOST

127.0.0.1

Bridge bind interface (hosted setups only)

FETCHPROXY_IDENTITY_DIR

~/.fetchproxy/identity/

Bridge identity keypair location

Troubleshooting

Run toast_healthcheck first.

  • "Forbidden" or "edge … refused": your browser hasn't passed Toast's Cloudflare check yet. Open order.toasttab.com, let it load (complete any check), then retry.

  • "No order.toasttab.com tab is open": open any order.toasttab.com/online/<restaurant> page in the browser that runs the extension.

  • "not signed in" / "sign-in has expired" (account tools): open or reload toast.app and sign in, then retry.

  • Directory comes back empty at night: nearbyRestaurants lists only restaurants open at when. Pass a daytime when.

Acknowledgement of terms

This server reaches Toast as you, through your browser, so Toast's guest terms of service govern how you use it. The maintainer has not reviewed those terms against this use. Read them yourself before you rely on this server. The project is not affiliated with or endorsed by Toast, Inc. It is for personal use: don't use it to bulk-harvest restaurant data.

Development

npm install
npm test        # typecheck + vitest (all mocked, no network)
npm run build   # typecheck + esbuild bundle → dist/bundle.js

License

MIT

Available Tools

9 tools
toast_find_restaurantsA
Read-onlyIdempotent

Find restaurants that take orders through Toast near a point (latitude/longitude — this server has no geocoder, so convert an address or city first). Returns each restaurant's GUID (what toast_get_menu needs), shortUrl, ordering link, address and distance, nearest first. Toast's directory lists restaurants OPEN for the dining option at when (default now): an empty or short result late at night means closed, not absent — retry with a daytime when. Optional name filters the results. There is no paging: total is every match and limit (default 25, max 300) is how many come back.

Inputs: latitude (required), longitude (required), name, view, +4 more.

toast_get_loyaltyA
Read-onlyIdempotent

Your Toast restaurant loyalty programs: for each, the restaurant, program name, balances (e.g. POINTS), and reward progress (target, left to target, whether a reward is available, Toast's own reward messages). Needs a toast.app sign-in in the browser running ContextMint Bridge.

Inputs: view.

toast_get_menuA
Read-onlyIdempotent

Get a Toast restaurant's menu: menus → groups → items with name, description, price, per-size prices and out-of-stock flag. restaurant is a GUID or any link that contains one (use toast_resolve_restaurant for a bare shortUrl). source: "online" (default) is what the restaurant sells through online ordering; "pos" is the register's full menu (often far larger); "both" merges them: an item on both menus is listed from the online menu with sources ["online","pos"]. An item filed under several groups ("Popular" plus its own category, say) appears under each, so total_items counts listings, not distinct items; dedupe by guid for a count. query searches item names, descriptions and group names. Prices are in dollars (12.5 = $12.50, checked against the ordering page). Modifier/option prices are not included.

Inputs: restaurant (required), view, limit, query, +2 more.

toast_get_orderA
Read-onlyIdempotent

One of your past Toast orders as a receipt: items with modifiers and price, subtotal, discounts, tax, tip, service charges, gift card applied, total (all dollars), payments (type, card brand, last 4), and delivery address/provider when it was delivered. Takes the restaurant and order GUIDs from toast_list_orders. Needs a toast.app sign-in in the browser running ContextMint Bridge.

Inputs: order_guid (required), restaurant_guid (required), view.

toast_get_walletA
Read-onlyIdempotent

Your Toast Cash: the available balance (stored value such as gifted Toast Cash included), the next expiry, the units that expire, and the units you have received (gifts name the sender). All amounts in dollars. Needs a toast.app sign-in in the browser running ContextMint Bridge.

Inputs: view.

toast_graphqlA
Read-onlyIdempotent

Run a read-only GraphQL QUERY against Toast's online-ordering gateway (ws-api.toasttab.com/do-federated-gateway) through your signed-in browser, and return its raw data and errors. For exploring fields the dedicated tools don't cover yet. Mutations and subscriptions are refused. Known-good operations: nearbyRestaurants(input:{diningOption,fulfillmentDateTime,latitude,longitude,radius}) and menusV3(input:{restaurantGuid,visibility}). Validation errors name the fields the schema lacks — use them to correct the query rather than guessing repeatedly.

Inputs: query (required), variables, operation_name.

toast_healthcheckVerify the ContextMint Bridge connection end-to-endA
Read-onlyIdempotent

Round-trips a small public ws-api.toasttab.com URL (/do-federated-gateway/v1/graphql?query=%7B__typename%7D) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real ws-api.toasttab.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke.

Inputs: no named parameters.

toast_list_ordersA
Read-onlyIdempotent

Your Toast order history, newest first: each order's GUID, restaurant (GUID, name, ordering link), when it was placed (ISO-8601 UTC, plus the restaurant's time zone), dining option and status as Toast reports them, item count with the first few items, and total in dollars. Pass next_page_token from the previous answer for older orders. Use toast_get_order for a full receipt. Needs a toast.app sign-in in the browser running ContextMint Bridge.

Inputs: view, page_size, next_page_token.

toast_resolve_restaurantA
Read-onlyIdempotent

Turn a Toast link, shortUrl, or GUID into the restaurant GUID that toast_get_menu needs. Links that carry a GUID (toast.app r- links, ?guid= parameters, bare GUIDs) resolve without a network call; an order.toasttab.com/online/ link or bare shortUrl is looked up in Toast by its slug. Returns guid: null with a next step when Toast does not know the slug.

Inputs: reference (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: wallet, loyalty, order history, order receipt, restaurant discovery, restaurant resolution, menu lookup, diagnostics, and a generic GraphQL fallback. The only overlap is that toast_graphql can query data covered by the dedicated tools, but its description frames it as an exploratory fallback, which limits misselection.

    Naming Consistency4/5

    All tools share the toast_ prefix and snake_case style, and most follow a verb_noun pattern such as toast_get_menu or toast_list_orders. The exceptions are toast_graphql and toast_healthcheck, which are noun-style names, but they remain readable and predictable.

    Tool Count5/5

    Nine tools is well within the appropriate range for this server's purpose, and each tool covers a distinct area: account balances, loyalty, orders, restaurant/menu discovery, diagnostics, and a generic query escape hatch. No tool feels redundant or excessive.

    Completeness4/5

    The read-only Toast surface is fairly complete: it covers wallet, loyalty, order history, order receipts, restaurant discovery, restaurant resolution, menus, diagnostics, and arbitrary read-only GraphQL exploration. Minor gaps remain, such as lack of direct geocoding or richer restaurant detail outside menus, but the GraphQL fallback and healthcheck reduce dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers