Restaurants: what an AI agent can and can't do with your software
- Last verified
- Updated Published
For owners, general managers and office staff at independent restaurants, cafés, bars and small groups who are wondering how far Meta's Muse or a similar assistant could get into the systems that run the front of house, the kitchen and the books, and which calls ought to stay with a manager.
How to read the status labels
| Label | What it means here |
|---|---|
| Confirmed by vendor | Taken from the software maker's or Meta's own material: developer docs, a help article, a pricing or partner page, or a company post. |
| Confirmed by the [agency] | Taken from a federal agency's website or a regulation that agency issued; the badge says which agency. |
| Reported | Said by somebody other than the vendor, for example a reseller or listing site, with nothing from the vendor to match. |
| Conflicting | Sources disagree with each other, and both versions are shown. |
| Unverified | We looked and couldn't settle it, or the only backing comes from outside the agencies our labels map. |
None of this comes from hands-on testing: we didn't plug any restaurant system into an agent. Treat each row as a lead to check against your own plan, account settings and contract. Our methodology page explains how we research.
The short version
- Meta's launch post for Muse names fifteen connectors. QuickBooks, Stripe and Klaviyo are there; no point of sale, reservation book, delivery service, scheduling app or inventory tool is. The post also points readers to the app's settings for every available connector. (Confirmed by vendor 1) That in-app list isn't visible to us, so a restaurant tool could appear there without our knowing. (Unverified)
- Three tools on this page publish their own MCP servers (the common plug that lets AI assistants call outside software): Square, still in Beta, plus 7shifts and MarginEdge, whose servers can only read. (Confirmed by vendor 8 22 25)
- Toast's self-serve route, Standard API access, is read-only and needs the RMS Essentials subscription or higher at every location. (Confirmed by vendor 6)
- Most reservation, waitlist and delivery APIs are built for approved software partners rather than for a single restaurant: OpenTable, Yelp, Uber Eats and Olo all route access through a partner program or written approval. (Confirmed by vendor 14 17 19 20)
- Tip pools, schedules for workers under 16, calorie and allergen statements, review requests, card data and marketing texts are where an agent's slip becomes a wage claim, a guest's health problem or a fine. Keep a manager on those; see the risk section.
Stack map
Point of sale and restaurant management
| Tool | In Meta's launch-post connector list? | Other route | Status and source |
|---|---|---|---|
| Toast | No | Standard API access gives read-only (GET) credentials per location, identified by the location's GUID, with no write access and no sandbox. Every location needs RMS Essentials or above, and the person setting it up needs the Manage Integrations permission. A management group can hold up to 100 credential sets. Read scopes cover orders, menus, labor and employees, cash management, configuration, stock, kitchen, guest personal information and more. Write access or a custom integration goes through your Toast rep or Customer Support. Toast says Standard API access comes with RMS for U.S. customers. | Confirmed by vendor 6 Toast itself publishes neither an MCP server nor a Zapier app that we could find. Unverified |
| Square for Restaurants | No | Square's MCP server (Beta) is hosted at mcp.squareup.com with OAuth sign-in, and you approve only the scopes you pick. Square says it reaches the whole Square API, customers, orders and items included. The hosted version works only against live production data; a copy you run yourself can point at a Sandbox and has a setting that blocks writes. Square suggests trying prompts in a Sandbox before going live, and it keeps an allowlist of MCP clients. Square also has a Zapier app. | Confirmed by vendor 8 27 Whether Muse is on Square's client allowlist, and how much of the restaurant-specific product the API reaches: Unverified |
| Clover | No | A REST API for inventory, orders and payments. Clover's merchant-specific API tokens are for sandbox testing only; live merchant data needs an app on the Clover App Market using OAuth tokens that expire. | Confirmed by vendor 10 Our search turned up no Clover MCP server and no Clover Zapier app. Unverified |
| SpotOn | No | SpotOn's integrations FAQ answers "No" to whether it has an open API. Developers apply through an intake form to become a Preferred Integration Partner, pass certification and then pilot with 5 to 10 merchants. Restaurants add approved integrations from the Marketplace in the SpotOn Dashboard; SpotOn says there's no blanket integration fee, but a small monthly fee applies if you opt out of its Core Bundle. | Confirmed by vendor 11 |
| Lightspeed Restaurant (K-Series) | No | Custom API access is a paid add-on arranged through your Account Manager, one API client per business account, and provisioning can take up to 48 hours. A custom integration gets only the Financial API and the Items API: no webhooks, and the orders and reservations scopes aren't available to it. Credentials point at production by default; a trial client with an empty demo account is available on request. Lightspeed lists more than 150 validated apps in its Integration Hub. | Confirmed by vendor 12 |
| TouchBistro | No | Its integrations page lists partners, including Restaurant365, MarginEdge, 7shifts, Push Operations, Deliverect, UrbanPiper and DoorDash online ordering. | Confirmed by vendor 13 We found no public API documentation from TouchBistro. Unverified |
Reservations and waitlists
| Tool | In Meta's launch-post connector list? | Other route | Status and source |
|---|---|---|---|
| OpenTable | No | Developers apply to its API partner program. The FAQ also says a restaurant can use the APIs directly by working with its account management team. The Directory API returns restaurant details and reservation links in JSON. | Confirmed by vendor 14 |
| Resy | No | Resy's integrations page groups its partners into point of sale and events, reservations and discovery, CRM, data and analytics, and winery and e-commerce. A banner on that page says Tock is now part of the Resy network. | Confirmed by vendor 15 We found no API a single restaurant can sign up for. Unverified |
| Tock | No | API keys and webhooks aren't included on every plan; Tock points you to Control Panel, Plan & Billing to check. The API offers data exports twice a day, guest profile uploads, and real-time webhooks for guest profiles and reservations. It can't create or cancel reservations, and the only thing you can write is basic guest information. An Account Owner requests a key by email. | Confirmed by vendor 16 |
| Yelp Guest Manager | No | Yelp's Waitlist Partner API is for companies that are already Yelp partners with Fusion API access, onboarded with Yelp's waitlist API team and the restaurant's Yelp customer success contact. It can list locations, check wait status, add a party to the queue, create "On My Way" visits, and read or cancel visits. | Confirmed by vendor 17 |
Online ordering and delivery
| Tool | In Meta's launch-post connector list? | Other route | Status and source |
|---|---|---|---|
| DoorDash Drive | No | An API for sending your own orders out with Dashers. Anyone with an email address can sign up and test in a sandbox; live credentials come after a demo and review with DoorDash, after which DoorDash says it gives an update on production access within 5 to 10 days, and you must accept its terms. Drive runs in the U.S., Canada, Australia and New Zealand, and DoorDash cites a limit of about 300 requests per 60 seconds. | Confirmed by vendor 18 |
| Uber Eats | No | Uber says access to these APIs may need its written approval. The steps include a developer account and sandbox, a nondisclosure and API licensing agreement, and sign-off from an Uber Eats partner manager. The APIs handle store status and hours, menu syncing, and accepting or denying orders; access tokens last 30 days. | Confirmed by vendor 19 |
| Olo | No | Olo describes more than 400 integrated partners and a Connect Partner Program with Standard, Gold and Platinum tiers; would-be partners start with an inquiry form. | Confirmed by vendor 20 We found no self-serve Olo API for a single restaurant. Unverified |
| ChowNow | No | Klaviyo, which is in Meta's list, documents a ChowNow integration. It syncs placed, accepted and cancelled order events every five minutes, pulls two years of history, and carries first and last names and phone numbers, but not email or SMS consent. | Confirmed by vendor 1 21 We found no public ChowNow API or Zapier app. Unverified |
Scheduling and payroll
| Tool | In Meta's launch-post connector list? | Other route | Status and source |
|---|---|---|---|
| 7shifts | No | An official public MCP server that is read-only: GET requests only, no POST, PUT, PATCH or DELETE. Reading real data needs an access token made under Company Settings, Developer Tools; 7shifts warns the token carries admin-level access, there's no sandbox, and it reads live wages, employee records and time punches. The limit is 10 requests a second per IP address. For OAuth apps, 7shifts sets a minimum plan per endpoint and answers with a 403 error if yours is below it; companies that joined from July 2, 2025 are on Comp, Essentials, Pro or Premium, and older accounts keep the earlier plan names. 7shifts also has a Zapier app. | Confirmed by vendor 22 27 |
| Homebase | No | A read-only API key, available only on the All in One plan. The account owner asks for one under Settings, API Access; Homebase says it typically answers within a business day. Homebase doesn't offer training on its API and advises against buying API access to link two systems that don't integrate. | Confirmed by vendor 23 |
Inventory, invoices and accounting
| Tool | In Meta's launch-post connector list? | Other route | Status and source |
|---|---|---|---|
| MarginEdge | No | A public API for pulling invoices, products, vendors, recipes, P&L and sales reports, but not for changing anything. It costs nothing extra on any subscription, a MarginEdge Admin generates the key, and each user gets one key. MarginEdge also runs an MCP server at mcp.marginedge.com that it says is read-only and has instructions for ChatGPT, Claude and Gemini. The MCP server answers only to users with the MarginEdge Admin or Franchisee Admin role and sees only the units that user can see. | Confirmed by vendor 24 25 Whether Muse can attach it as a custom connector: Unverified |
| Restaurant365 | No | The Classic API is read-only. The newer R365 Public API is an Early Adopter program that is closed to new participants. An OData connector feeds Excel, Power BI and Domo for users with the Accounting Clerk or Full Access role; it exposes employees, labor detail, sales and transactions, limits sales queries to 31 days, and has sales and labor figures only after the Daily Sales Summary is polled. | Confirmed by vendor 26 |
| QuickBooks | Yes | According to Intuit, the Muse connector lets you review profit and loss, cash flow and the balance sheet, show top customers and products, send invoices customers can pay, and chase overdue ones. Payroll, closing the books and taxes stay in QuickBooks itself. | Confirmed by vendor 1 4 |
| Stripe | Yes | Stripe's MCP server reads and writes through its API with OAuth or an agent API key. Stripe asks a person to confirm some writes, such as refunds and outbound payments, and says that from December 2026 the server will accept only agent API keys or an OAuth connection. | Confirmed by vendor 1 5 |
Everything above except QuickBooks, Stripe and Klaviyo is absent from the connectors Meta named, so linking any of them to Muse means a custom connector, unless the in-app list proves otherwise. Meta lets you build those, says it doesn't review them, and warns that what Muse pulled through a connector can remain in its memories and chat history after you disconnect. (Confirmed by vendor 2) Meta's guidelines for published connectors require approval on every use of a sensitive write, ask for a read-only option where OAuth allows, bar adding tips or fees without authorization, and say Meta isn't approving new money-movement tools for now. (Confirmed by vendor 3) A custom connector you write yourself skips Meta's review, so keeping its scope narrow is on you.
Jobs you could hand off today (per vendor docs)
| Job | Tool | What the vendor says | Status and source |
|---|---|---|---|
| Compare last week's food cost, invoices and P&L across locations | MarginEdge MCP in ChatGPT, Claude or Gemini | Its server reads invoices, vendor pricing and margins and can't change records. | Confirmed by vendor 25 . Inside Muse: Unverified |
| See who is scheduled, who clocked in and what labor cost this week | 7shifts MCP | It reads schedules, wages and time punches with an admin-level token. | Confirmed by vendor 22 . Inside Muse: Unverified |
| Pull yesterday's orders and menu items for a sales question | Toast Standard API access, behind a custom connector | Read scopes include orders and menus, location by location. | Confirmed by vendor 6 . Inside Muse: Unverified |
| Look up an order or a customer in Square | Square MCP | OAuth with scopes you choose; a self-run copy can be held to reads. | Confirmed by vendor 8 . Inside Muse: Unverified |
| Review cash flow and overdue catering invoices | QuickBooks in Muse | Intuit lists both. | Confirmed by vendor 4 |
| Check a card payment or start a refund for a guest | Stripe MCP | A refund waits for a person's confirmation. | Confirmed by vendor 5 |
| Study reservation trends from guest and booking data | Tock exports and webhooks | Exports run twice a day; the API can't book or cancel. | Confirmed by vendor 16 |
Keep these out
- Keys that can change the POS. Square's hosted MCP server touches only live data, and the read-only switch Square documents belongs to the copy you run yourself. (Confirmed by vendor 8) Toast's self-serve credentials can't write at all. (Confirmed by vendor 6) Start read-only, and let a manager make menu, price and discount changes in the POS.
- Wage and staff records. A 7shifts token for its MCP server is admin-level, has no sandbox, and reads live pay rates, staff records and punches. (Confirmed by vendor 22) Anything an agent reads can end up in its memory (see Meta's note above), so decide who in the company should see pay data before you connect.
- Card numbers. Stripe says card type, last four digits and expiry date fall outside PCI requirements, while a business that takes raw card numbers itself may face more than 300 security controls. (Confirmed by vendor 28) Never paste a guest's full card number into a chat, a note or a reservation comment.
- Guest phone lists without consent. Klaviyo says texts can't go to numbers that came in from its ChowNow sync unless consent is gathered separately. (Confirmed by vendor 21) An agent shouldn't turn an order history into a text campaign.
- Surprise add-ons. Meta's guidelines tell connectors not to add products, tips, subscriptions or fees that weren't authorized. (Confirmed by vendor 3) Hold your own connector to the same standard, and keep service charges and tip prompts set by a person.
Risks to keep a person on
- Tip credit, tip pools and service charges. The DOL's tipped-worker fact sheet sets the federal cash wage floor at $2.13 an hour and the largest tip credit at $5.12 against the $7.25 federal minimum. An employer must tell tipped staff five things before taking the credit, may cut a card tip only by the card company's processing percentage, and must treat a compulsory service charge as wages rather than a tip. Where state law is more protective, it governs. (Confirmed by the DOL 29) Under 29 CFR 531.52 and 531.54, an employer can't keep employees' tips whether or not it takes a credit, managers and supervisors can't share in other employees' tips, and pooled tips must be paid out no later than the regular payday for the workweek. When a credit is taken, the pool is limited to staff who customarily and regularly get tips; a pool that adds cooks or dishwashers is allowed only where everyone gets the full minimum wage. (Confirmed by the DOL 31) Fact Sheet #15B says a manager who meets the executive duties test, including an owner with at least a 20 percent stake who manages, can't take from a pool even on a shift spent tending bar. (Confirmed by the DOL 30) A spreadsheet an agent builds to split tips is a payroll decision; have a manager check who is in the pool and sign off on the payout.
- Schedules for 14- and 15-year-olds. Under 29 CFR 570.35, they may work outside school hours only: up to 3 hours on a school day (Fridays included), 18 hours in a school week, 8 hours on a non-school day and 40 hours in a non-school week, and only between 7 a.m. and 7 p.m., or 9 p.m. from June 1 through Labor Day. (Confirmed by the DOL 32) Many states set tighter limits or add rules for 16- and 17-year-olds; we haven't sourced any state here. (Unverified) If an agent drafts the schedule, a manager should check every minor's shifts against both.
- Calories on menus at chains. 21 CFR 101.11 covers restaurants in a chain of 20 or more locations under one name selling substantially the same items, plus places that register to be covered. Menus include electronic menus and menus on the Internet. Calories must appear beside each standard item's name or price, the menu must carry the statement "2,000 calories a day is used for general nutrition advice, but calorie needs vary," and the business needs a reasonable basis, such as a nutrient database, cookbook or lab analysis, for its numbers. (Confirmed by the FDA 33) If an agent rewrites your online menu, it mustn't invent or round calorie figures; take them from your nutrition analysis.
- Allergens. The FDA says FALCPA named eight major food allergens (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat and soybeans), and the FASTER Act added sesame as the ninth, effective January 1, 2023. The FDA enforces FALCPA's labeling on most packaged foods; its list of exclusions includes most food sold at retail or food service establishments that isn't pre-packaged with a label. (Confirmed by the FDA 34) That exclusion doesn't make a wrong answer safe. An agent replying to a guest about what's in a dish can't see cross-contact in your kitchen; route those questions to the kitchen manager. State and local rules on allergen notices in restaurants vary, and we haven't sourced them. (Unverified)
- Food safety rules. The FDA Food Code is a model that local, state, tribal and federal regulators use to write their own retail and food service rules; the FDA calls the 2026 edition its newest full edition. (Confirmed by the FDA 35) Which edition your state or county has adopted, and with what changes, we haven't checked. (Unverified) Temperature logs and date marks are records an inspector may rely on; they should come from the person who took them.
- Reminder and marketing texts. The FCC's rule in section 64.1200 requires the called party's prior express consent before an autodialed or prerecorded call reaches a cell phone, paragraph (a)(1)(iii), and prior express written consent once those calls advertise, paragraph (a)(2). Before November 25, 2026, the rule says an opt-out must be honored however it's reasonably made, and the one confirming text it permits has to be a one-time message, free of marketing and the only one sent after the request. (Confirmed by the FCC 37) From November 25, 2026, the FCC's revised rule lets a sender name one exclusive opt-out channel, provided it's disclosed clearly: a voice or keypad prompt, one of the standard reply words such as "stop" or "unsubscribe," or a website or phone number. Senders must still honor opt-outs within ten business days. An opt-out from a purely informational text may be applied to that category only, while one from a promotional message ends all promotional messages. The confirming text must still carry no marketing and keeps the five-minute presumption, but it no longer has to be one-time or the sole follow-up message. (Confirmed by the FCC 38) Keep "your table is ready" texts free of promotions, and don't let an agent text guests a deal unless you hold written consent.
- Card data and the POS. Toast says every customer taking cards must be PCI compliant, and that for card-present payments on Toast-approved devices the only requirement left to the restaurant in its card-present matrix is restricting physical access to cardholder data. (Confirmed by vendor 7) Square says it meets PCI DSS on sellers' behalf, so they don't have to validate compliance individually. (Confirmed by vendor 9) Stripe calls PCI compliance a responsibility shared between it and the business, which must attest every year. (Confirmed by vendor 28) These are vendor statements about their own systems; they don't cover a spreadsheet, inbox or chat where an agent copies card details.
- Delivery app fees. Some cities limit what delivery apps may charge restaurants. We haven't sourced any such cap or checked whether one applies where you are, so ask your city or a lawyer before an agent compares fees or changes delivery settings. (Unverified)
- Reviews. The FTC's rule at 16 CFR part 465 bars a business from writing or buying reviews that misrepresent who wrote them or their experience (465.2), from offering anything in return for reviews of a particular sentiment, positive or negative (465.4), and from using threats or false accusations to stop or remove a review (465.7). (Confirmed by the FTC 36) Meta's guidelines also say connectors must not fabricate reviews. (Confirmed by vendor 3) Don't let an agent post reviews, offer a free dessert for five stars, or answer a bad review with threats. Asking every guest for honest feedback is a different thing.
This guide isn't legal, tax or food safety advice. Your health department, state labor agency, card processor and software contracts can impose stricter terms than anything listed here.
FAQ
Can Muse get into my Toast or Square data today? Meta's launch post names neither of them as a connector. (Confirmed by vendor 1) Toast offers read-only API credentials and Square an MCP server, so a custom connector is the route for either. (Confirmed by vendor 6 8) We haven't confirmed that Muse can attach Square's server. (Unverified)
Which restaurant tools already plug into AI assistants? Square (Beta), 7shifts and MarginEdge each document an MCP server, and the 7shifts and MarginEdge servers only read. (Confirmed by vendor 8 22 25) None of the three names Muse as a supported client. (Unverified)
Could an agent book or cancel reservations for me? Not through Tock's API, which can't create or cancel reservations. (Confirmed by vendor 16) OpenTable and Yelp open their APIs to approved partners, although OpenTable says restaurants can also arrange access through account management. (Confirmed by vendor 14 17)
Could an agent build next week's schedule? The 7shifts MCP server can read schedules but not change them. (Confirmed by vendor 22) If an agent drafts one elsewhere, check minors' hours and break rules before you publish it.
What's a low-risk first step? Connect QuickBooks in Muse and ask about cash flow and overdue invoices. Nothing in your POS changes.
Where are the other trades? See all trade guides.
Changes to this page
| Date | Change | Source |
|---|---|---|
| 2026-10-28 | Page published. | All 38 sources listed above, checked 2026-10-28. |
Seen a mistake or a stale line? Report it on our Corrections page. This page restates published vendor and agency material; none of these tools was tested by us.
Sources
- Source 6: Toast “Toast API access: user guide, requirements, scopes and credentials; Standard API Access.” doc.toasttab.comAlso: https://doc.toasttab.com/doc/devguide/devApiAccessRequirements.html, https://doc.toasttab.com/doc/devguide/devApiAccessScopes.html, https://doc.toasttab.com/doc/devguide/devApiAccessCredentials.html, https://support.toasttab.com/en/article/Standard-API-Access
- Source 9: Square Support Center “Review Square's security and data encryption features.” squareup.com
- Source 10: Clover Developer Docs “Making REST API calls; Create a merchant-specific API token.” docs.clover.comAlso: https://docs.clover.com/dev/docs/gdp-create-merchant-specific-api-token
- Source 11: SpotOn “SpotOn integrations (FAQ) and Central API certification process.” spoton.comAlso: https://developers.spoton.com/central-api/docs/certification-process
- Source 12: Lightspeed “Custom integrations (Lightspeed Restaurant K-Series API portal).” api-portal.lsk.lightspeed.app
- Source 22: 7shifts Developers “7shifts MCP server; plan requirements.” developers.7shifts.comAlso: https://developers.7shifts.com/docs/plan-requirements
- Source 24: MarginEdge Help Center “MarginEdge Public API; access errors with the Public API or MCP server.” help.marginedge.comAlso: https://help.marginedge.com/hc/en-us/articles/55405358841491-Why-Am-I-Getting-an-Access-Error-When-Using-the-MarginEdge-Public-API-or-MCP-Server
- Source 25: MarginEdge Help Center “Connecting your [me] data to your AI Platform.” help.marginedge.com
- Source 27: Zapier “Square integrations; 7shifts integrations.” zapier.comAlso: https://zapier.com/apps/7shifts/integrations
- Source 29: U.S. Department of Labor, Wage and Hour Division “Fact Sheet #15: Tipped Employees Under the Fair Labor Standards Act (FLSA).” dol.gov
- Source 30: U.S. Department of Labor, Wage and Hour Division “Fact Sheet #15B: Managers and Supervisors Under the Fair Labor Standards Act (FLSA) and Tips.” dol.gov
- Source 31: eCFR (U.S. Department of Labor regulation) “29 CFR Part 531, Wage Payments Under the Fair Labor Standards Act (sections 531.52, 531.54 and 531.59).” ecfr.gov
- Source 32: eCFR (U.S. Department of Labor regulation) “29 CFR Part 570, Child Labor Regulations (section 570.35).” ecfr.gov
- Source 33: eCFR (FDA regulation) “21 CFR 101.11, Nutrition labeling of standard menu items in covered establishments.” ecfr.gov
- Source 36: eCFR (FTC regulation) “16 CFR Part 465, Use of Consumer Reviews and Testimonials (sections 465.2, 465.4 and 465.7).” ecfr.gov
- Source 38: Federal Communications Commission, in the Federal Register “Enhancing the Ability of Consumers To Control the Robocalls (FR Doc. 2026-21821, 91 FR 67214).” federalregister.gov