MCP tools and capabilities
Understand the restaurant data available to a Fiest AI connection after you approve access.
Fiest gives an AI application a small set of purpose-built tools instead of unrestricted database or network access. Every call stays inside the restaurant or Management organization you approved.
The exact list shown in your application depends on the connection, the scopes you approved, and which capabilities Fiest has enabled in that environment.
Restaurant and organization context
| Tool | What it does |
|---|---|
get_restaurant_context | Confirms one authorized restaurant and the current member role. |
get_organization_context | Lists the restaurants included in an approved Fiest Management connection, including configured business identities. |
compare_restaurant_sales | Compares a bounded date range across 2–10 restaurants from the same approved Management connection. |
get_restaurant_profile | Returns bounded business context such as timezone, first order, and connected payment-provider status without credentials. |
For an organization connection, pass only a restaurant ID returned by
get_organization_context. Fiest rejects restaurants outside the approved
connection.
Sales, accounting, and orders
| Tool | What it does |
|---|---|
get_sales_summary | Summarizes up to 31 days of gross and net sales, VAT, refunds, discounts, orders, and optional daily or payment-method breakdowns. |
get_accounting_summary | Produces an accounting-oriented summary with payment methods, VAT, refunds, and reconciled sales totals. |
find_orders | Searches bounded order history using supported filters and receipt identifiers. |
get_order_details | Returns the bounded details of one authorized order without payment credentials. |
get_order_trends | Analyzes order timing, item types, and peak periods over a bounded range. |
Inventory
| Tool | What it does |
|---|---|
get_inventory_status | Shows current stock and low-stock status. |
get_inventory_movements | Shows bounded stock movement history. |
MCP and Partner API are separate
MCP is designed for interactive AI applications and uses the MCP server as its OAuth resource. The Fiest Partner API is a separate server-to-server integration surface with its own audience, scopes, and published OpenAPI contract.
An MCP token cannot call the Partner API, and a Partner API token cannot call MCP. New MCP tools do not automatically become public Partner API endpoints; Partner API operations are published separately after their contract and authorization model have been reviewed.