OFW MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DATA_DIR | No | Persistent data directory used for confirmation nonces and default session-token location on mcp-host. | |
| OFW_PASSWORD | No | Your OurFamilyWizard account password for the env-var authentication path. | |
| OFW_USERNAME | No | Your OurFamilyWizard account email address for the env-var authentication path. | |
| OFW_CACHE_DIR | No | Directory for the local SQLite message cache. | ~/.cache/ofw-mcp |
| OFW_UPLOAD_DIR | No | Directory from which ofw_upload_attachment uploads local files. | ~/Downloads/ofw-mcp |
| OFW_WRITE_MODE | No | Structural write gate. One of none, drafts, or all. Unrecognized values fail closed to none. | all |
| MCP_CONFIRM_MODE | No | Controls gated writes on clients that cannot show a confirmation prompt. One of ask-user, auto, or refuse. Unrecognized values are treated as refuse. | ask-user |
| OFW_AUTO_REFRESH | No | Set to true to have read tools sync and answer instead of refusing when an empty result comes from an unverified cache. | |
| OFW_EXPENSE_ONLY | No | Set to true to register only ofw_healthcheck and expense tools. Unrecognized non-empty values fail closed to the restricted state. | |
| OFW_SESSION_FILE | No | Path to the stored session token file. | $MCP_DATA_DIR/.ofw-mcp/session.json |
| MCP_CONFIRM_SECRET | No | Signing key for confirmation tokens. Defaults to a random per-process value; set it only if tokens must survive a server restart. | |
| OFW_CACHE_IDENTITY | No | Optional label used to give separate OFW accounts separate local caches. | |
| OFW_ALLOW_MARK_READ | No | Deployment-wide ceiling for marking messages read. Set to false to prevent any tool from stamping First Viewed on unread inbox messages. | |
| OFW_ATTACHMENTS_DIR | No | Directory for downloaded message attachments. | ~/Downloads/ofw-mcp |
| OFW_CALENDAR_WRITES | No | Set to true to register calendar create/update/delete tools when OFW_WRITE_MODE=drafts. Redundant in all mode and never overrides none. | |
| OFW_DISABLE_FETCHPROXY | No | Set to 1 to skip the fetchproxy/ContextMint Bridge fallback entirely, making missing credentials a hard error. | |
| MCP_CONFIRM_ELICITATION | No | Set to off to disable confirmation prompts so every client uses the MCP_CONFIRM_MODE path. Any other value stays on. | on |
| MCP_CONFIRM_TTL_SECONDS | No | How long a server-side confirmation token stays valid, in seconds. | 600 |
| MCP_HOST_CONFIRM_SECRET | No | Host-supplied stable confirmation-token signing key, used on mcp-host. | |
| OFW_EXPENSE_UPLOAD_ONLY | No | Set to true for the strictest expense mode: only ofw_healthcheck, ofw_upload_expense_pdf, ofw_create_expense, and ofw_update_expense. Implies OFW_EXPENSE_ONLY. | |
| OFW_FETCH_UNREAD_BODIES | No | Set to true to make ofw_sync_messages fetch unread bodies by default. Capped by OFW_ALLOW_MARK_READ. | |
| OFW_FRESHNESS_TTL_SECONDS | No | Freshness threshold in seconds for cached message and draft reads. Unusable values fall back to the default. | 300 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| toast_find_restaurantsA | 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 |
| toast_resolve_restaurantA | 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. |
| toast_get_menuA | Get a Toast restaurant's menu: menus → groups → items with name, description, price, per-size prices and out-of-stock flag. |
| toast_graphqlA | 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. |
| toast_list_ordersA | 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. |
| toast_get_orderA | 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. |
| toast_get_loyaltyA | 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. |
| toast_get_walletA | 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. |
| toast_healthcheckA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.