Turn it on in three steps.
Open AI visibility
In your panel, under AI visibility — this is where MCP lives alongside your public page settings.
Switch on reading
One toggle publishes your MCP address. Ordering and table requests are separate toggles, left off unless you turn them on.
Share the address
It’s shown in your panel and on your public page, ready for a guest to paste into their assistant.
A read-only connector, with ordering as a separate switch.
One address, nothing to install
Turn it on in your panel and get one MCP endpoint. No server to run, no code to maintain — it always reflects today’s menu.
Off by default, per tenant
Reading, table requests and ordering are three separate switches, all off until you turn them on — nothing is exposed by accident.
Only what you entered
Menu, prices, allergens, open/closed state, delivery zones and fees — from your data, never invented. A blank field comes back as unknown.
Orders need your consent, twice
A draft is priced against your real menu first; only the exact confirmed total can be submitted, and it still reaches you unconfirmed like any other order.
See the public side of it
Every venue with AI visibility on has a public page showing exactly what an assistant would read — open the live demo restaurant’s to see it.
Common questions.
Yes — this page is the setup side. The feature page explains what a guest’s assistant can actually do once connected.
No. They paste your MCP address into an assistant they already use — Claude, ChatGPT, or their own agent.
No. If you allow ordering, the assistant can submit only the exact total it already quoted the guest from your menu — and the order still arrives unconfirmed, exactly like one from your website.
Be the restaurant an assistant can read.
14 days free · No credit card · Live in 5 minutes