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

Source: https://elaichi.ai/connectors/restaurant365/

## Facts

| | |
| --- | --- |
| Application | Restaurant365 |
| Category | Accounting |
| AI tools | 61 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Restaurant365 is connected

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

## Connect Restaurant365 in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Restaurant365.
2. Optionally set Share with, then press Connect.
3. Paste a Restaurant365 API key. One person generates a token in Restaurant365 and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Restaurant365 tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Restaurant365 MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Restaurant365 MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Restaurant365 tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Restaurant365 through Elaichi

### Enter a week of vendor invoices at once

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

### Record vendor credits for short deliveries

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

### Check GL balances before month end close

Finance. Ask which GL accounts moved this month, compare balances across locations, and list the AP payments that went out and from which bank account.

### Compare daily sales across every location

Operations. Pull yesterday's daily sales for each brand and location group in Restaurant365 and ask which stores came in under plan.

### Spot gaps in the latest inventory count

Kitchen. Open the most recent inventory count and ask which item categories look off against the one before it, before the order goes in.

### Pull an employee roster by location

HR. List the employees in Restaurant365 for a given store or brand so a manager can check who is on the books before scheduling.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Restaurant365 connection?

Yes. One person connects Restaurant365 in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every call.

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

## All 61 Restaurant365 tools

Every tool below is callable through https://api.elaichi.ai/mcp once Restaurant365 is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Restaurant365 ap attachment upload URL** (Create). Generate Upload URL: Step 1 of 3. Returns a pre-signed Amazon S3 URL that accepts exactly one file — the size and MIME type declared in this request — together with the generated storage file name needed in step 3. Then PUT the file to the returned url outside the connector (pre-signed Amazon S3, not R365) and register it with ap_attachments.create. Needs the R365 permissions Accounts Payable → AP Invoices → Edit AP Invoices and Accounts Payable → AP Credit Memos → Edit AP Credit Memos and Accounts Payable → AP Payments → Edit AP Payments. Required: fileName, fileType, fileSizeBytes.
- **Create a Restaurant365 ap attachment** (Create). Register Attachment: Step 3 of 3. Links a file already uploaded to Amazon S3 in step 2 to an existing AP transaction. Attachments must be enabled for the organization; if they are not, this endpoint returns 403. First ap_attachment_upload_urls.create, then a PUT of the file to its S3 url. Required: formId, formName, newFileName, fileName, fileType, uploadType, userId.
- **Restaurant365 ap credit memos bulk create** (Create). AP Credit Memos: Creates one or more AP credit memos in bulk. Each credit memo's detail lines are either GL-account-based or item-based, determined by the vendor's entry type. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Credit Memos → Create AP Credit Memos. Required: creditMemos.
- **Restaurant365 ap credit memos bulk update** (Update). AP Credit Memos: Updates one or more AP credit memos. Currently supports updating the approval status to Approved. Failures are isolated — a failed item does not prevent the others from being applied. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Credit Memos → Approve AP Credit Memos. Required: creditMemos.
- **List all Restaurant365 ap credit memos** (List). AP Credit Memos: Retrieves credit memos. If no filter of any kind is supplied, results are limited to the current day (UTC). Needs the R365 permission Accounts Payable → AP Credit Memos → View AP Credit Memos Within Accounting or Food → AP Credit Memos → View AP Credit Memos Within Food. Paged (limit sets pageSize, max 250).
- **Restaurant365 ap invoices bulk create** (Create). AP Invoices: Creates one or more AP invoices in batch. Each invoice's detail lines are either GL-account-based or item-based, determined by the vendor's entry type — not by a request flag. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Invoices → Create AP Invoices or Food → AP Invoices → Create AP Invoices (Food equivalent). Required: invoices.
- **Restaurant365 ap invoices bulk update** (Update). AP Invoices: Partial update AP Invoices in batch. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Invoices → Approve AP Invoices or Food → AP Invoices → Approve AP Invoices (Food equivalent).
- **List all Restaurant365 ap invoices** (List). AP Invoices: Retrieves invoices. If no filter of any kind is supplied, results are limited to the current day (UTC). Needs the R365 permission Accounts Payable → AP Invoices → View AP Invoices Within Accounting or Food → AP Invoices → View AP Invoices Within Food. Paged (limit sets pageSize, max 250).
- **Restaurant365 ap payments bulk create** (Create). AP Payments: Create AP Payments in batch. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Payments → Create Manual AP Payments. Required: payments.
- **Restaurant365 ap payments bulk update** (Update). AP Payments: Partial update AP Payments in batch. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Accounts Payable → AP Payments → Approve AP Payments.
- **List all Restaurant365 ap payments** (List). AP Payments: Retrieves payments. If no filter of any kind is supplied, results are limited to the current day (UTC). Needs the R365 permission Accounts Payable → AP Payments → View AP Payments. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 bank accounts** (List). Bank Accounts: Retrieves bank accounts for the current tenant with filtering and pagination support. Needs the R365 permission Banking → Bank Accounts → View Bank Accounts. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 brand location groups** (List). Brand Location Groups: Retrieves a paginated list of brand location groups with their subgroups and location assignments. Needs the R365 permission Administration → View Brand Manager. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 brands** (List). Brands: Retrieves the list of brands that the authenticated tenant is connected to. A tenant is connected to a brand when it has subscribed to one or more of that brand's services. Needs the R365 permission Administration → View Brand Manager.
- **List all Restaurant365 connected tenants** (List). Connected Tenants and Locations: Retrieves a paginated list of tenants and their locations that have subscribed to the authenticated brand. Security: No permission is documented for this endpoint. Access is gated at the instance level — the endpoint rejects requests from an instance that does not own a brand. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 daily sales** (List). Daily Sales: Retrieves a single daily sales summary with its paginated sales tickets for the specified business date and location. Each page is one record: the summary with a page of its salesTickets. Needs the R365 permission Sales & Cash → Daily Sales → View Daily Sales. Required: businessDate, location. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 deleted entities** (List). Deleted Entities: Retrieves deleted entity references within a specified date range. At least one of deletedOnStart or deletedOnEnd is required. When only one boundary is provided, the query is scoped to that single day. Needs the R365 permission Administration → Audit Log → View Audit & SMS Log. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 employees** (List). Employees: Retrieves a paged list of employees with enriched job and location data. At least one date filter (ModifiedOnStart or ModifiedOnEnd) and at least one location scope (locations or legalEntities) are required. Needs the R365 permission Labor → Employees → View Employees. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 gl account balances** (List). GL Account Balance by Date: Retrieves GL account balances as of specified date. Lists locations with their balances. Needs the R365 permissions General Ledger → GL Accounts → View GL Accounts and General Ledger → GL Accounts → Access Restricted GL Accounts. Required: date. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 gl accounts** (List). GL Accounts: Retrieves GL Accounts. Needs the R365 permission General Ledger → GL Accounts → View GL Accounts. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 inventory count by ID** (Get). Inventory Count by ID: Retrieves a single inventory count by identifier. Each count contains only the items present on that count, not every item with inventory activity. Needs the R365 permission Food → Inventory Counts → View Inventory Counts and View Variance Tab. Required: id.
- **List all Restaurant365 inventory counts** (List). Inventory Counts: Retrieves a list of inventory counts matching the supplied filter and pagination criteria, sorted by last modified date and time. Needs the R365 permission Food → Inventory Counts → View Inventory Counts and View Variance Tab. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 item category by ID** (Get). Item Category by ID: Retrieves a specified item category. Needs the R365 permission Food → Item Categories → View Item Categories. Required: id.
- **List all Restaurant365 item categories** (List). Item Categories: Retrieves a list of item catgories. Needs the R365 permission Food → Item Categories → View Item Categories. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 item transfer by ID** (Get). Item Transfer by ID: Retrieves a specified item transfer. Needs the R365 permission Food → Item Transfers → View Item Transfers. Required: id.
- **List all Restaurant365 item transfers** (List). Item Transfers: Retrieves a list of item transfers. Needs the R365 permission Food → Item Transfers → View Item Transfers. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 item by ID** (Get). Item by ID: Retrieves a specified purchase item. Needs the R365 permission Food → Purchased Items → View Purchased Items. Required: id.
- **List all Restaurant365 items** (List). Items: Retrieves a list of purchase items. Needs the R365 permission Food → Purchased Items → View Purchased Items. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 jobs** (List). Jobs: Retrieves a paged list of job titles with location, GL account, and responsibility data. At least one date filter (ModifiedOnStart or ModifiedOnEnd) is required. Needs the R365 permission Labor → Jobs → View Jobs. Paged (limit sets pageSize, max 250).
- **Restaurant365 journal entries bulk create** (Create). Journal Entries: Creates journal entries in batch. Journal entry numbers are not required to be unique — duplicate numbers are allowed and will create separate records. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission General Ledger → Journal Entries → Create Journal Entries. Required: journalEntries.
- **List all Restaurant365 labor punches** (List). Labor Punches: Retrieves a paginated list of labor punches. At least one date range (DateOfBusiness or ModifiedOn) must be supplied. Needs the R365 permission Labor → Punch Edits → Add/Edit/Delete Labor Punches or Labor → Employees → Time → View Punches or Labor → Employees → Employment → Hourly Pay Rates → View Hourly Pay Rates or Labor → Employees → Employment → Salary Pay Rates → View Salary Pay Rates. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 legal entity by ID** (Get). Legal Entity by ID: Retrieves a single legal entity by identifier. Needs the R365 permission Administration → Legal Entities → View Legal Entities. Required: id.
- **List all Restaurant365 legal entities** (List). Legal Entities: Retrieves a list of legal entities for a tenant. At least one of modifiedOnStart or modifiedOnEnd must be provided. Needs the R365 permission Administration → Legal Entities → View Legal Entities. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 locations** (List). Locations: Retrieves a list of locations. Needs the R365 permission Administration → Locations → View Locations. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 payment terms** (List). Payment Terms: Retrieves payment terms for the current tenant with pagination support. Needs the R365 permission Accounts Payable → Payment Terms → View Payment Terms. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 payroll summaries** (List). Payroll Summaries: Retrieves payroll summaries for a date range, filtered by location or legal entity. Needs the R365 permissions Administration → Legal Entities → View Legal Entities and Locations → View Locations and Labor → Employees → View Employees and Labor → Jobs → View Jobs and Time & Attendance → Timecards → View Timecards. Required: businessDateStart, businessDateEnd.
- **List all Restaurant365 pos mapping groups** (List). POS Mapping: Retrieves POS Mappings grouped by type (Sales Account, Payment Type, Job, Paid Out) with enriched data including GL accounts, location, and legal entity. Returns one object (the mappings grouped by type), not a list. Needs the R365 permission Administration → POS Management → View/Edit POS Mapping Tool.
- **List all Restaurant365 pos mappings** (List). POS Mappings: Retrieves POS Mappings. Returns all POS mappings with their associated GL Account (null if unmapped). Needs the R365 permission Administration → POS Management → View/Edit POS Mapping Tool. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 purchase order by ID** (Get). Purchase Order by ID: Retrieves a specified purchase order. Needs the R365 permission Food → Purchasing → View Purchase Orders. Required: id.
- **List all Restaurant365 purchase orders** (List). Purchase Orders: Retrieves a list of purchase orders. Needs the R365 permission Food → Purchasing → View Purchase Orders. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 reporting role by ID** (Get). Reporting Role by ID: Retrieves a single reporting role by its unique identifier. Needs the R365 permission Administration → Users → View Report Roles. Required: id.
- **List all Restaurant365 reporting roles** (List). Reporting Roles: Retrieves a paginated list of reporting roles for the tenant, optionally filtered by brand name. Needs the R365 permission Administration → Users → View Report Roles. Paged (limit sets pageSize, max 250).
- **List all Restaurant365 sales forecasts** (List). Sales Analytics: Retrieves published forecast sales. Maximum date range is 14 days; a wider range returns 400. Note: despite the name, most interval fields are labor metrics and the whole jobDetails array is per-job labor. Returns one object (the location and its daily data), not a list. Needs the R365 permission Sales & Cash → Forecasts → Weekly Forecasting → View Weekly Forecasting. Required: locationId, startDate, endDate.
- **List all Restaurant365 transactions** (List). Transactions: Retrieves transactions. At least one complete date range must be provided: ModifiedOn (ModifiedOnStart and ModifiedOnEnd) or DateOfBusiness (DateOfBusinessStart and DateOfBusinessEnd). Security: Access is evaluated per transaction type. The requesting user must have the View permission for each transaction type they want included in the response. Required: LocationId. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 units of measure by ID** (Get). Unit of Measure by ID: Retrieves a specified unit of measure. Needs the R365 permission Food → Units of Measure → View Units of Measure. Required: id.
- **List all Restaurant365 units of measure** (List). Units of Measure: Retrieves a list of units of measure. Needs the R365 permission Food → Units of Measure → View Units of Measure. Paged (limit sets pageSize, max 250).
- **Get single Restaurant365 user role by ID** (Get). User Role by ID: Retrieves a single user role by its unique identifier. Needs the R365 permission Administration → Users → View User Roles & Permissions. Required: id.
- **List all Restaurant365 user roles** (List). User Roles: Retrieves a paginated list of user roles for the tenant, optionally filtered by brand name. Needs the R365 permission Administration → Users → View User Roles & Permissions. Paged (limit sets pageSize, max 250).
- **Restaurant365 users bulk create** (Create). Users: Creates one or more users. Returns 409 Conflict for duplicate usernames or emails, and 422 for invalid field values. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Administration → Users → Create Users. Required: users.
- **Restaurant365 users bulk update** (Update). Users: Partially updates multiple users in a single request. Takes an array; if any item fails, the connector returns an error naming the failed and the succeeded items. Needs the R365 permission Administration → Users → Edit Users or Administration → Users → Edit Users in Bulk. Required: users.
- ...and 11 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
