Restaurant365 MCP connector
The Restaurant365 connector brings AP invoices, credit memos, payments, daily sales, GL balances and inventory counts to Claude, ChatGPT, Cursor and Microsoft Copilot, with every call running as the signed-in person and landing in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
Show yesterday's daily sales for every location, grouped by brand.
Working in Restaurant365 with Elaichi
-
List all Restaurant365 ap credit memos
-
List all Restaurant365 ap invoices
-
List all Restaurant365 ap payments
How to connect Restaurant365 to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Restaurant365 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.
Restaurant365 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.
Restaurant365 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.
Restaurant365 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.
Restaurant365 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 Restaurant365 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 Restaurant365 through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Restaurant365 is logged.
-
Accounts payable
Enter a week of vendor invoices at once
Hand the agent the invoices from a delivery run and it creates them in Restaurant365 in one pass, with the scanned copy attached to each one.
-
Accounts payable
Record vendor credits for short deliveries
When a vendor shorts a case or two, raise the credit memos in Restaurant365 together instead of one at a time, and update them when the vendor confirms.
-
Finance
Check GL balances before month end close
Ask which GL accounts moved this month, compare balances across locations, and list the AP payments that went out and from which bank account.
-
Operations
Compare daily sales across every location
Pull yesterday's daily sales for each brand and location group in Restaurant365 and ask which stores came in under plan.
-
Kitchen
Spot gaps in the latest inventory count
Open the most recent inventory count and ask which item categories look off against the one before it, before the order goes in.
-
HR
Pull an employee roster by location
List the employees in Restaurant365 for a given store or brand so a manager can check who is on the books before scheduling.
Try asking
- “Show yesterday's daily sales for every location, grouped by brand.”
- “List AP invoices due this week and who the vendors are.”
- “Compare the latest inventory count against last week's by item category.”
What connecting Restaurant365 gets you
6 screens from Elaichi, each doing one job for your Restaurant365 account.
Ask Elaichi to work across your apps.
Show yesterday's daily sales for every location, grouped by brand.
List AP invoices due this week and who the vendors are.
Compare the latest inventory count against last week's by item category.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about invoices and sales in plain words.
Three starter prompts pull live Restaurant365 invoices, daily sales and GL balances.
Copy the endpoint
AI apps
Use Restaurant365 from Claude, ChatGPT or Cursor.
One governed endpoint, no SDK and no shared API key, every person signed in as themselves.
Tool catalog
61 Restaurant365 tools, no connector code to write.
AP invoices, credit memos, payments, daily sales, GL accounts and inventory counts, ready on day one.
Toolboxes
Every team gets its own Restaurant365 toolbox.
Accounts payable works invoices, operations reads daily sales, each from a toolbox scoped to them.
Shared connections
Share one Restaurant365 connection, never the key.
One controller connects, teams and members work through it, and nobody else sees the API key.
Audit log
Every Restaurant365 call is logged with a name.
When, who, what happened and which invoice 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.
Restaurant365 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch ap invoices
Restaurant365
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
Restaurant365
Queued
Workflows
A schedule drafts the AP digest, you approve.
New Restaurant365 invoices are fetched, grouped by vendor, summarized, approved, then posted back.
Restaurant365 health
Refreshed 4 minutes ago · every 15 minutes · from the ap invoices collection
Ap invoices
1,284 ↓ 12%
Credit memos
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Ap invoices created
Last 14 days
By team
Share of activity
AP team 34%
Finance 27%
Operations 21%
Brand East 18%
Collections and dashboards
Restaurant365 health numbers, refreshed on a schedule.
Four metrics, fourteen days of invoices created and a breakdown by team, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Restaurant365
All three can connect Restaurant365 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 Restaurant365 tools | Allow or restrict single Restaurant365 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 Restaurant365 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.
Restaurant365 tools for your AI agents
61 tools are ready to call through Elaichi's MCP endpoint the moment you connect Restaurant365, 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 Restaurant365 to Claude?
Two steps. In Elaichi, add the Restaurant365 connector and paste in your Restaurant365 API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi and Restaurant365 is ready.
Does Restaurant365 work with ChatGPT and Cursor as well as Claude?
Yes. Restaurant365 is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. Each person signs in as themselves whichever client they use.
What can an AI agent actually do with my Restaurant365 data?
It can list and create AP invoices, credit memos and payments in Restaurant365, attach documents to invoices, and read daily sales, GL accounts and balances, bank accounts, employees, inventory counts and item categories. So you can ask for yesterday's sales by location, enter a batch of vendor invoices, or compare GL balances before close. Short concrete asks work better than long paragraphs.
Does connecting Restaurant365 give the AI everything in my books?
No. The agent only sees what the person who signed in can already see in Restaurant365, so a store manager's view stays a store manager's view. Elaichi can narrow that further by role or by person, and it never widens it.
Can I stop an agent from creating or changing things in Restaurant365?
Yes. Restrictions in Elaichi apply per action, on a role or on one person, so you can allow reading daily sales while restricting the creation or update of AP invoices, credit memos and payments in Restaurant365. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Restaurant365 connection when someone leaves?
Offboarding a person in Elaichi ends their access to Restaurant365 at once, in every client. A shared Restaurant365 connection keeps working for everyone else on the team. Disconnecting Restaurant365 once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Restaurant365 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Restaurant365 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 Restaurant365?
Yes. Both let Claude, ChatGPT or Cursor use Restaurant365. 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 Restaurant365 call.
How is Elaichi different from Composio for Restaurant365?
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 Restaurant365: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Restaurant365 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