AI connection overview (MCP)

Connect Claude, ChatGPT, Claude Code, or Codex to restaurant data you approve in Fiest without creating an API key.

Pick your application, copy one command or server address, and approve access in Fiest. You do not need to create or paste an API key.

Choose your application

Fiest currently provides one public MCP endpoint for live Fiest accounts. Internal development and beta endpoints are not part of the public MCP service.

Claude Code

Copy and run:

claude mcp add --scope user --transport http \
  fiest https://mcp.fiest.io/mcp

Continue with Claude Code authentication →

Codex

Copy and run:

codex mcp add fiest --url https://mcp.fiest.io/mcp

Continue with Codex authentication →

Claude or ChatGPT

Copy the Fiest server address when your application asks for an MCP endpoint:

https://mcp.fiest.io/mcp

ChatGPT

Create a Fiest app in an eligible workspace.

Approve access in Fiest

Your application opens a secure Fiest page:

Sign in to Fiest if needed.
Choose one restaurant, or use Fiest Management to review organization-wide access.
Review the requested permissions and approve or deny the connection.
Return to your application.

If you are already signed in to the correct Fiest service, the browser can continue directly to selection and consent. Otherwise, Fiest asks you to sign in first.

Keep authentication in the browser

Never paste a Fiest password, one-time code, access token, refresh token, or authorization code into an AI chat. The application should open the official Fiest authorization flow for you.

Restaurant and organization access

Connection	What it can access	Where to manage it
Restaurant	One selected Fiest restaurant	Dashboard → Profile → Connections → AI connections
Organization	The restaurants reviewed together in Fiest Management	Management → Settings → AI connections

An organization authorization does not silently include restaurants added later. Reauthorize the connection to review and include newly onboarded restaurants.

Fiest exposes bounded tools for restaurant context, sales, accounting, orders, inventory, opening hours, menus, and catalog imports. The exact tools available depend on the access you approve and the capabilities Fiest has released for your connection.

Tools and capabilities

Review the available read and write operations, their access boundaries, and the confirmation rules for changes.

Partner API

Build a server-to-server integration with the separate Fiest Partner API.

Check that it worked

Ask the application:

Use Fiest to show the restaurant context I authorized.

You are connected when the application calls get_restaurant_context and shows the restaurant or organization you approved.

Remove access

Revoke a restaurant connection from Dashboard → Profile → Connections → AI connections. Revoke an organization connection from Fiest Management settings. Revocation invalidates the stored authorization. Reconnect through OAuth if you want to use Fiest again.

Payment corrections

Fiest can expose payment-method corrections for bookkeeping when the approved connection has the matching accounting capability. The correction changes the allocation of an existing payment between methods; it does not create another sale, VAT amount, refund, or bank settlement.

Use both reports for the same restaurant and inclusive business period:

Read get_accounting_summary for the raw totals, VAT, refunds, tips, deferrals, reconciliation, and payment-method totals.
Read get_payment_report for the raw and, when safe, adjusted payment allocations. Use the same restaurant, dates, currency, timezone, and business-day cutoff for both calls.
Continue only when the reports are balanced, the payment report is ready, and the VAT and tender evidence is complete. A review_required or blocked_stale report must stay out of the ledger.
Import the ready adjusted methods in place of the raw method totals. Keep the accounting summary's sales, refund, VAT, tip, and deferral semantics; never add raw and adjusted rows together.

For a repeat import, retain the prior snapshots and correction IDs. An unchanged snapshot produces no new allocation, while an undone correction produces the inverse allocation. If the raw accounting baseline changed, reconcile it before applying a payment-only reclassification.

See Payment corrections for the Partner API contract, report fields, role restrictions, receipt/order/tab/split identifiers, and the full reconciliation rules.

Owners, admins, and managers can also correct a proven payment through MCP when the connection has the separately approved fiest.accounting.corrections.write scope together with fiest.restaurant.read, fiest.accounting.read, and fiest.analytics.read, and the environment enables writes. Correction writes are enabled in internal beta. Production remains disabled pending its separate rollout. Use get_payment_correction_workspace to find a payment by business day or calendar month and receipt hash or source ID. Call preview_payment_correction, show the before and after report, and wait for the user's approval before apply_payment_correction. Use an undo preview followed by undo_payment_correction to reverse that payment's correction. Preserve the preview fingerprint, revision, expiry, and input, and supply confirmed: true with a UUID idempotency key. For a Management portfolio connection, first use get_management_context and pass the authorized organizationId and restaurantId to every correction call.

Undo requires the source payment to remain valid and present. If it was later voided, unconfirmed, removed, or otherwise changed, MCP leaves the undo for manual review. The tool removes the allocation transfer only; it does not repair or recreate the original sale, VAT, refund, or provider record.

The server rechecks current access and source evidence before saving. Missing VAT, refunds, and unproven splits still require review; MCP cannot repair those by guessing values. Read and reconcile both reports again after a change.

MCP tools and capabilities

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 to 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.
`get_opening_hours`	Returns the complete weekly schedule and its version without changing it.

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`	Returns raw accounting totals, including payment methods, VAT, refunds, and reconciliation. Dashboard payment corrections are not applied to these method totals.
`get_payment_report`	Prepared for beta: returns raw and nullable adjusted payment allocations for one business day or a bounded calendar month, with explicit readiness and review warnings.
`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.

Menus and catalog imports

Tool	What it does
`find_menu_items`	Finds exact menu-item UUIDs and current availability using bounded filters.
`list_menus`	Lists menus with stable UUIDs, live state, and current category and item counts.
`get_catalog_import_guide`	Returns the supported create-only catalog model and workflow.
`get_catalog_creation_capabilities`	Reports the catalog limits and semantics currently available to the connection.
`get_catalog_import_target`	Inspects one exact target menu before an import is planned.
`plan_menu_import`	Validates a bounded create-only catalog document without applying it.
`apply_menu_import`	Applies the unchanged reviewed plan idempotently after confirmation.
`get_menu_import_result`	Returns the result and server-issued UUIDs for an import action.

Menu changes are available only when Fiest has approved the matching write scope for the connection. The tools require exact UUIDs from fresh reads, explicit confirmation, idempotency keys, and current versions or counts where the operation can conflict with another change.

Tool	What it does
`create_menu`	Creates one empty inactive draft without publishing it.
`add_existing_items_to_menu`	Adds reviewed existing items to one inactive draft.
`get_draft_menu_item_edit_target`	Inspects one exact draft item, whether it is editable, and its current opaque version.
`update_draft_menu_item`	Updates reviewed fields on one unshared item in one inactive draft after confirmation.
`set_active_menu`	Replaces the active POS menu after the current state and target are reviewed.
`set_online_menu`	Replaces the online-ordering menu after the current state and target are reviewed.

Direct item editing never changes a live or shared item and never publishes a menu. If the item version or menu counts change after review, Fiest rejects the write and requires a fresh inspection.

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 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. Fiest publishes Partner API operations separately after reviewing their contract and authorization model.

Connect Fiest to Claude Code

Claude Code supports remote MCP servers over Streamable HTTP and can complete Fiest OAuth in your browser.

1. Copy and run this command

claude mcp add --scope user --transport http \
  fiest https://mcp.fiest.io/mcp

User scope makes the connection available across your Claude Code projects.

2. Approve access in Fiest

Start browser authorization from your terminal:

claude mcp login fiest

You can also open Claude Code and run:

/mcp

Select the fiest connection and start authentication. Claude Code opens the Fiest authorization flow in your browser. Sign in if needed, choose the restaurant or organization you want to connect, review access, and approve it.

No credentials to configure

Do not add an API token, client secret, or one-time code. Authentication happens on the official Fiest page opened by Claude Code.

3. Check that it worked

Ask Claude Code:

Use Fiest to show the restaurant context I authorized.

You are connected when Claude Code calls get_restaurant_context and shows the restaurant or organization you approved.

Manage the connection

claude mcp list
claude mcp get fiest
claude mcp remove fiest

Use /mcp to inspect status, authenticate again, or clear Claude Code's stored authentication. Revoking access in Fiest remains the authoritative way to remove the grant.

Troubleshooting

Authentication required: run claude mcp login fiest. You can also open /mcp, select the connection, and authenticate.
Browser did not open: copy the authorization URL shown by Claude Code and open it in your browser.
Connection was revoked: authenticate again through /mcp.
Wrong restaurant: revoke the Fiest authorization and reconnect, selecting the correct restaurant.

See the official Claude Code MCP documentation for client-specific options.

Connect Fiest to Codex

The Codex app, Codex CLI, and Codex IDE extension share MCP configuration when they run on the same Codex host.

1. Copy and run this command

codex mcp add fiest --url https://mcp.fiest.io/mcp

You can also add the server in the Codex app from Settings → MCP servers → Add. Choose Streamable HTTP and copy the address shown above.

2. Approve access in Fiest

Restart Codex if the new server does not appear immediately. Open the MCP server list, select Fiest, and choose Authenticate. Codex opens the Fiest authorization flow in your browser.

You can start the same flow from your terminal:

codex mcp login fiest

Codex requests the scopes advertised by the Fiest MCP server. Sign in if needed, choose one restaurant or review an organization connection, then approve the requested access shown by Fiest.

No credentials to configure

Do not add an API token, client secret, or one-time code. Authentication happens on the official Fiest page opened by Codex.

3. Check that it worked

Ask Codex:

Use Fiest to show the restaurant context I authorized.

You are connected when Codex calls get_restaurant_context and shows the restaurant or organization you approved.

Manage the connection

codex mcp list
codex mcp get fiest
codex mcp remove fiest

You can also inspect authentication and available tools from the Codex MCP server screen or /mcp.

Troubleshooting

Server needs authentication: open the MCP server screen and authenticate, or rerun the matching login command above.
Authentication expired: authenticate again. Fiest keeps tokens bound to the exact MCP resource instead of accepting a less secure unbound refresh.
Server was just added: restart Codex, then inspect /mcp.
Authorization was revoked in Fiest: authenticate again.
Wrong restaurant: revoke the grant in Fiest and reconnect with the intended restaurant.

See the official Codex MCP documentation for client-specific configuration.

Connect Fiest to Claude

Claude supports remote MCP servers as custom connectors. The available controls depend on your Claude plan and organization role.

Copy the server address

Use the public Fiest MCP endpoint:

https://mcp.fiest.io/mcp

Individual Pro or Max

Open Claude and go to Customize → Connectors.
Select +, then Add custom connector.
Name the connector Fiest.
Paste the Fiest server address.
Add the connector, then select Connect.
Complete Fiest sign-in, selection, and consent in the browser.

Leave advanced OAuth client credentials empty. Fiest supports automatic OAuth client setup for Claude.

Team or Enterprise

An Owner or Primary Owner first adds the connector:

Open Organization settings → Connectors.
Select Add, then Custom → Web.
Paste the Fiest server address and add the connector.

Each member then opens Customize → Connectors, finds Fiest, and selects Connect to authorize their own Fiest access.

Check that it worked

Enable Fiest for the conversation from the + menu → Connectors. Then ask:

Use Fiest to show the restaurant context I authorized.

You are connected when Claude calls get_restaurant_context and shows the restaurant or organization you approved.

Authorize only on Fiest

Claude should redirect you to the official Fiest authorization page. Never paste a password, one-time code, or token into a Claude conversation.

Troubleshooting

Add connector is unavailable: your plan or organization role may not permit custom connectors. Ask the workspace owner.
Fiest is connected but unavailable in chat: enable it for the current conversation from the + menu.
Access was revoked: select Connect again and repeat Fiest authorization.

See Anthropic's custom connector guide for current plan and role details.

Connect Fiest to ChatGPT

ChatGPT can use Fiest through a custom MCP app. Custom app creation depends on your ChatGPT plan, workspace settings, and role.

Before you begin

Your workspace must allow custom apps and developer mode. Business and Enterprise/Edu administrators control availability and publishing.

If you cannot see Create in Settings → Apps, ask your workspace administrator to enable custom MCP apps or create Fiest for the workspace.

1. Copy the server address

Use the public Fiest MCP endpoint:

https://mcp.fiest.io/mcp

2. Create the app

Open Settings → Apps → Create. Administrators can also use Workspace settings → Apps → Create.
Name the app Fiest.
Paste the Fiest server address as the MCP endpoint.
Choose OAuth authentication.
Select Scan tools.
Complete Fiest sign-in, restaurant or organization selection, and consent when the browser prompt opens.
Finish creating the app.

Fiest advertises refresh access through standard OAuth discovery so supported clients can keep the connection active without asking you to sign in for every session.

3. Check that it worked

Open a new chat and select Fiest from the tools or apps menu. Ask:

Use Fiest to show the restaurant context I authorized.

You are connected when ChatGPT calls get_restaurant_context and shows the restaurant or organization you approved.

Do not share credentials in chat

Fiest authentication happens in the browser window opened by ChatGPT. Never paste a password, one-time code, access token, or authorization code into a ChatGPT conversation.

Publish for a workspace

Administrators can review the draft in Workspace settings → Apps → Drafts and publish it to approved users. Review the available tools and action controls before publishing. New or changed write tools should remain disabled until the workspace has reviewed them.

Troubleshooting

Create is missing: developer mode or custom apps are not enabled for your account or workspace.
Tool scan asks for authorization: complete the Fiest OAuth flow in the browser, then wait for the scan to finish.
The app is not available in chat: select it from the tools menu, or ask an administrator to publish or enable it.
Authorization was revoked: reconnect Fiest from the app's settings.

See the official OpenAI guides for developer mode and MCP apps and apps in ChatGPT.

AI connection overview (MCP)

Claude

ChatGPT

Tools and capabilities

Partner API

On this page