Connect an AI assistant
You can connect an AI assistant to Menuro and ask about your business in plain language: “how did we do yesterday”, “what was in order 1052”, “is the lamb biryani sold out”, “has this number ordered before”. The assistant uses an MCP (Model Context Protocol) server, which is the standard way AI assistants connect to outside services. The connection is read-only: the assistant can look things up, but it cannot change anything.
Who can connect
Section titled “Who can connect”Anyone with the Admin, Co-Admin, Outlet Owner or Outlet Manager role. You sign in with the same email and password you use for your admin dashboard, and the assistant then sees exactly what your role can see:
- Admins and co-admins see the whole business.
- Outlet owners and managers see only their own outlet.
Every other role, every device login and every customer account is refused at sign-in. If your role changes, the assistant’s access follows it within a minute.
The server address
Section titled “The server address”| If your admin dashboard is on | Server address |
|---|---|
| Supaorder | https://mcp.supaorder.com/mcp |
| SuperApp | https://mcp.superapphq.com/mcp |
| Menuro | https://mcp.menuro.io/mcp |
The instructions below use the Menuro address, https://mcp.menuro.io/mcp.
What the assistant can read
Section titled “What the assistant can read”| Area | What it answers |
|---|---|
| Orders | Orders in any date range of up to 31 days, filtered by status, outlet or channel, and any single order in full: items, totals, payment, delivery and timeline |
| Sales | Order count, gross sales, average order value, tips and cancellation rate, by day, outlet, channel or order type, and your best-selling dishes |
| Menu | Categories and dishes with prices, sold-out and temporarily-off state, and per-channel price overrides |
| Customers | Customers matching part of a name, phone number or email, with their order history and wallet and reward balances |
What it cannot do:
- It cannot change orders, the menu, availability, customers or settings. There is no tool that writes.
- It never shows a customer’s full phone number or email. Contact details are always masked, for every role, and nothing turns that off.
- It never returns payment credentials or gateway keys.
Connect your assistant
Section titled “Connect your assistant”- In Claude (claude.ai or Claude Desktop), open Customize → Connectors and choose Add custom connector. On a Team or Enterprise plan, an owner adds it under Organization settings → Connectors.
- Paste
https://mcp.menuro.io/mcpas the server URL and choose Add. - Choose Connect, sign in with your admin dashboard email and password, and choose Allow.
Add the server, then sign in from inside Claude Code with /mcp:
claude mcp add --transport http menuro https://mcp.menuro.io/mcpAdd https://mcp.menuro.io/mcp as a custom connector in ChatGPT’s settings. You sign in with your
admin dashboard email and password when ChatGPT first uses it.
Open this link in a browser on the computer where Cursor is installed:
cursor://anysphere.cursor-deeplink/mcp/install?name=menuro&config=eyJ1cmwiOiJodHRwczovL21jcC5tZW51cm8uaW8vbWNwIn0=Or add it to ~/.cursor/mcp.json yourself:
{ "mcpServers": { "menuro": { "url": "https://mcp.menuro.io/mcp" } } }Open this link to install it in VS Code:
vscode:mcp/install?%7B%22name%22%3A%22menuro%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.menuro.io%2Fmcp%22%7DOr add it to .vscode/mcp.json:
{ "servers": { "menuro": { "type": "http", "url": "https://mcp.menuro.io/mcp" } } }Add it to your MCP configuration file (mcp_config.json):
{ "mcpServers": { "menuro": { "serverUrl": "https://mcp.menuro.io/mcp" } } }gemini mcp add --transport http menuro https://mcp.menuro.io/mcpThe sign-in page opens the first time Gemini uses the server.
Disconnect
Section titled “Disconnect”In your admin dashboard, open the account menu at the bottom of the sidebar and choose Disconnect AI assistants. It lists every assistant connected to your account, with when each was connected and last used. Disconnect all revokes all of them at once, and the next request from any of them is refused.
Removing the connector inside the assistant only removes it there. Use Disconnect AI assistants to make sure the access itself is gone.
Related: Integrations overview · Users & roles · Reports
Was this page helpful?
This site uses a chat widget that sets a cookie so it can keep your conversation. It runs no analytics. See the privacy policy.