Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Toasttab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Toast restaurants and menus: find places that order via Toast, read online or register menus.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user toasttab-mcp '--' npx -y toasttab-mcp
# 2 — ask your agent for something these tools do
# toast_list_orders, toast_get_order, toast_get_loyalty and 6 more
Toasttab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Toasttab as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user toasttab-mcp '--' npx -y toasttab-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take TOAST_WS_PORT (Overrides the fetchproxy WebSocket port (default 37149, the fleet-shared port).), FETCHPROXY_WS_HOST (Bridge bind interface, a literal IP only (anything else is ignored); default 127.0.0.1. Keep on loopback — it exists for a hosted child in its own network namespace.), FETCHPROXY_IDENTITY_DIR (Where to store the long-term bridge identity keypair, an absolute path only (anything else is ignored); default ~/.fetchproxy/identity/. Exists for a host that runs a separate child per caller.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_size | integer | no | Orders per page (1–50, default 20). |
| next_page_token | string | no | From a previous answer, to fetch the next (older) page. |
| view | yes | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| restaurant_guid | yes | — | |
| order_guid | yes | — | |
| view | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | GraphQL document containing only queries/fragments. |
| variables | object | no | Variables object, if the document declares any. |
| operation_name | string | no | Which operation to run, if the document has several. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| restaurant | string | yes | Restaurant GUID, or a Toast link containing one. |
| source | string | no | — |
| query | string | no | Only items whose name/description/group contains this (case-insensitive). |
| include_out_of_stock | boolean | no | Keep 86'd items (flagged out_of_stock). Default true. |
| limit | integer | no | Max items to return (default 200). |
| view | yes | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| latitude | number | yes | Latitude of the search centre, decimal degrees. |
| longitude | number | yes | Longitude of the search centre, decimal degrees. |
| radius_miles | number | no | Search radius in miles (0.1–25, default 2). Toast caps one answer at 300 restaurants. |
| name | string | no | Only restaurants whose name contains this (case/punctuation-insensitive). |
| dining_option | string | no | TAKE_OUT (default) or DELIVERY. DELIVERY lists only restaurants that deliver to the point. |
| when | string | no | ISO-8601 date-time the order would be fulfilled at. Default: now. |
| limit | integer | no | Max restaurants to return (default 25). |
| view | yes | — |
Turn a Toast link, shortUrl, or GUID into the restaurant GUID that toast_get_menu needs. Links that carry a GUID (toast.app r-<guid> links, ?guid= parameters, bare GUIDs) resolve without a network call; an order.toasttab.com/online/<shortUrl> link or bare shortUrl is looked up in Toast by its…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference | string | yes | A Toast ordering link, toast.app link, restaurant GUID, or shortUrl slug. |
Check the browser bridge and Toast gateway end to end.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Toasttab or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Toasttab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.