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
Use Production for a live Fiest account. Use Sandbox only when Fiest has
invited you to test with isolated sample data. The sandbox currently uses the
temporary mcp-dev.fiest.io hostname.
Claude Code
Copy and run:
claude mcp add --scope user --transport http \
fiest https://mcp.fiest.io/mcpContinue with Claude Code authentication →
Codex
Copy and run:
codex mcp add fiest --url https://mcp.fiest.io/mcpContinue with Codex authentication →
Claude or ChatGPT
Copy the Fiest server address when your application asks for an MCP endpoint:
https://mcp.fiest.io/mcpApprove 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.
What Fiest can do
Fiest exposes bounded tools for restaurant context, sales, accounting, orders, and inventory. 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.