Toast MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOAST_MCP_MODE | No | Mode of operation: 'demo' (default) or 'live'. | demo |
| TOAST_CLIENT_ID | No | Toast OAuth client ID for live mode. | |
| TOAST_CLIENT_SECRET | No | Toast OAuth client secret for live mode. | |
| TOAST_MCP_TRANSPORT | No | Transport type: 'http' for HTTP transport, otherwise stdio (default). | |
| TOAST_API_ACCESS_URL | No | Toast-provisioned API access URL, used in live mode. | |
| TOAST_RESTAURANT_GUIDS | No | Comma-separated list of restaurant GUIDs for live mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| toast_get_verification_statusA | Explains whether this server is using safe demo data or customer-supplied live Toast credentials, and what has been verified. |
| toast_get_api_coverageA | Lists every current Toast-hosted public API family and distinguishes implemented read coverage from catalog-only APIs that require Toast access and validation. |
| toast_list_locationsA | Lists the demo restaurant or the explicitly configured live Toast restaurant locations. |
| toast_find_ordersA | Returns privacy-minimized order summaries for an ISO 8601 time range of at most 31 days. |
| toast_get_orderA | Gets one order by Toast GUID, excluding customer identity, contact, delivery, and payment-card fields. |
| toast_search_menuA | Searches resolved Toast Menus V2 item names, groups, menus, PLUs, and SKUs. |
| toast_get_inventoryB | Reads Toast Stock API inventory. Live responses normally contain OUT_OF_STOCK and QUANTITY items only. |
| toast_show_operations_overviewA | Builds a privacy-safe sales and inventory overview and renders an interactive MCP App when supported. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Toast operations overview app | Interactive, privacy-safe operations overview for the toast_show_operations_overview tool. |
TDQS
Scored across 8 tools
Each tool targets a distinct resource or meta-information area, so confusion is unlikely. Minor overlap exists between find_orders and get_order (plural vs singular) and between get_inventory and show_operations_overview, but descriptions clarify scope.
All tools use the consistent 'toast_' prefix and mostly follow verb_noun naming (get_, list_, find_, search_). 'show_operations_overview' slightly breaks the verb pattern but remains intuitive and aligned with the others.
Eight tools is well within the optimal range and appropriately scoped for a focused Toast POS read-oriented MCP server. Each tool adds meaningful functionality without unnecessary redundancy.
The set covers core read operations for locations, orders, menu, inventory, and an overview, which is reasonable for a privacy-safe server. However, it lacks write/update operations and many Toast API families beyond the ones listed, leaving the surface notably incomplete for full Toast platform coverage.