Toast MCP connector
Connect Toast to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can read your restaurants' checks, orders, payments, menus, and payouts as the person who signed in, with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Total payments for the downtown restaurant last Friday
Working in Toast with Elaichi
-
List all Toast metrics
-
List all Toast restaurants informations
-
List all Toast checks
How to connect Toast to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Toast MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Toast MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Toast MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Toast MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Toast MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Toast to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Toast through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Toast is logged.
-
Operations
Check on every restaurant before the huddle
Ask for last night's checks and payments across all your Toast restaurants and get one plain-language rundown before the morning meeting, without opening each location one at a time.
-
Finance
Reconcile payouts against payments
Pull the payouts, payout payments, and sales dates for a week and set them next to the guest payments Toast recorded, so the numbers that go to the accountant already match.
-
Kitchen
Compare menus across locations
List the menus at each restaurant, spot items and prices that drift between locations, and create a corrected price when the chef signs off.
-
Front of house
Find an open check fast
Ask which checks are still open at a restaurant, or open a new check for a walk-in group, while the manager is still on the floor.
-
People
Log labor and review shift coverage
Record a labor entry after a shift and list the week's labor by restaurant, so scheduling conversations start from what actually happened.
-
Leadership
Track metrics across the restaurant group
List the restaurants in a group alongside their orders and payments, and record a metric for the board pack without a spreadsheet in between.
Try asking
- “Total payments for the downtown restaurant last Friday”
- “Which menu items appear on the most open checks today?”
- “Summarize this week's payouts across all group restaurants”
What connecting Toast gets you
6 screens from Elaichi, each doing one job for your Toast account.
Ask Elaichi to work across your apps.
Total payments for the downtown restaurant last Friday
Which menu items appear on the most open checks today?
Summarize this week's payouts across all group restaurants
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about last night's checks in plain language.
Answers come from live Toast orders, payments, and menus, not from a stale export.
Copy the endpoint
AI apps
Toast in Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot, connected once.
One governed endpoint for every MCP client, with no SDK and no shared API key.
Tool catalog
117 Toast tools, ready without writing code.
Checks, orders, payments, menus, payouts, labor, and restaurants, covered from the first day.
Toolboxes
Every team gets its own Toast toolbox.
Finance sees payouts, kitchen sees menus, and each toolbox is scoped to one team.
Shared connections
Share one Toast connection, never the API key.
One manager connects, teams and members work through it, and nobody sees a credential.
Audit log
Every Toast call is logged with a name.
When, who, what happened, and which check or payment, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Toast digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch checks
Toast
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Toast
Queued
Workflows
A schedule closes the day, a person approves.
Nightly checks are fetched, grouped by restaurant, drafted into a digest, approved, then posted to Toast.
Toast health
Refreshed 4 minutes ago · every 15 minutes · from the checks collection
Checks
1,284 ↓ 12%
Orders
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Checks created
Last 14 days
By team
Share of activity
Downtown 34%
Airport 27%
Catering 21%
Finance 18%
Collections and dashboards
Toast sales health, computed without a model.
Four metrics, fourteen days of orders, and a breakdown by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Toast
All three can connect Toast to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Toast tools | Allow or restrict single Toast tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Toast call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Toast tools for your AI agents
117 tools are ready to call through Elaichi's MCP endpoint the moment you connect Toast, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Toast to Claude?
First connect Toast in Elaichi by pasting a Toast API key. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Toast is available in your next conversation.
Does Toast work with ChatGPT and Cursor as well as Claude?
Yes. Once Toast is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Toast once and every client picks it up.
What can an AI agent actually do with my Toast data?
With Toast connected, an agent can list your restaurants, pull checks, orders, payments, and payouts for a location or a date range, read the menus at each site, and record new checks, labor entries, prices, payouts, and metrics on your behalf. Short, concrete asks like "payments at the downtown restaurant yesterday" work better than long paragraphs.
Does connecting Toast give the AI access to every restaurant?
No. Every call to Toast runs inside the access of the person who signed in, so an agent can only see the restaurants and records that person can already see in Toast. Elaichi can narrow that further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Toast?
Yes. Restrictions in Elaichi work per action, so you can allow reading checks and payments while restricting anything that creates a check, a price, or a payout in Toast. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Toast connection when someone leaves?
Offboarding a person in Elaichi ends their access to Toast at once, in every client they used. A Toast connection they shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Toast once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.
Does the Toast MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Toast is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Toast?
Yes. Both let Claude, ChatGPT or Cursor use Toast. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Toast call.
How is Elaichi different from Composio for Toast?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Toast: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Toast in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot