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

Environment

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, or Fiest sandbox when using the sandbox.
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.