# AI connection overview (MCP)

Source: https://docs.fiest.io/mcp

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 [#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.

### Production

**Claude Code**

    Copy and run:

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

    [Continue with Claude Code authentication →](/mcp/claude-code)

    **Codex**

    Copy and run:

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

    [Continue with Codex authentication →](/mcp/codex)

    **Claude or ChatGPT**

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

    ```text
https://mcp.fiest.io/mcp
```

    <Cards>
      <Card title="Claude" href="/mcp/claude">
        Add the server as a custom connector.
      </Card>

      <Card title="ChatGPT" href="/mcp/chatgpt">
        Create a Fiest app in an eligible workspace.
      </Card>
    </Cards>

### Sandbox

**Claude Code**

    Copy and run:

    ```bash
claude mcp add --scope user --transport http \
  --client-id fiest-claude-code-dev --callback-port 33177 \
  fiest-sandbox https://mcp-dev.fiest.io/mcp
```

    [Continue with Claude Code authentication →](/mcp/claude-code)

    **Codex**

    Copy and run:

    ```bash
codex mcp add fiest-sandbox --url https://mcp-dev.fiest.io/mcp
```

    [Continue with Codex authentication →](/mcp/codex)

    **Claude or ChatGPT**

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

    ```text
https://mcp-dev.fiest.io/mcp
```

    <Cards>
      <Card title="Claude" href="/mcp/claude">
        Add the server as a custom connector.
      </Card>

      <Card title="ChatGPT" href="/mcp/chatgpt">
        Create a Fiest app in an eligible workspace.
      </Card>
    </Cards>

## Approve access in Fiest [#approve-access-in-fiest]

Your application opens a secure Fiest page:

1. Sign in to Fiest if needed.
2. Choose one restaurant, or use Fiest Management to review organization-wide
   access.
3. Review the requested permissions and approve or deny the connection.
4. 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.

<Callout type="warn" title="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.
</Callout>

## Restaurant and organization access [#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 [#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.

<Cards>
  <Card title="Tools and capabilities" href="/mcp/tools">
    Review the available read and write operations, their access boundaries,
    and the confirmation rules for changes.
  </Card>

  <Card title="Partner API" href="/api">
    Build a server-to-server integration with the separate Fiest Partner API.
  </Card>
</Cards>

## Check that it worked [#check-that-it-worked]

Ask the application:

```text
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 [#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.