Rosuii and your AI assistant
Connect your Rosuii account to ChatGPT or Claude and ask about your own restaurant the way you would ask a manager. How many plates of kacchi sold last week. Among dishes that sold this month, which five sold least by quantity. The assistant reads the answer from your own live data, not from a report you have to export first.
Spoken in Bangla · Watch on YouTube
Four steps in an assistant that supports this connection. Check the assistant provider’s account and device requirements separately.
In ChatGPT or Claude, add a connector and give it the Rosuii address: https://api.rosuii.com/v1/mcp. The assistant registers itself with Rosuii automatically; there is no key to copy and no developer account to create.
The assistant sends you to Rosuii's own sign-in page. You log in there, not in the chat window. Approval requires a restaurant admin account or settings.edit permission. Rosuii shows the permitted actions on the consent screen. Your password is typed into Rosuii and never reaches the assistant.
The consent screen is built from your own account. An owner sees the full list; a manager who cannot view reports is not offered the sales tools at all. If you are assigned to one branch, orders, sales, staff and dish availability all stay inside it. Menu descriptions and the public profile are restaurant-level, so they are not divided by branch.
Type a question in Bangla or English. The assistant picks the right tool, reads your data and answers. Before requesting an edit, ask to see the wording first. Rosuii does not enforce a separate draft-approval step, and a save immediately changes the public website.
Permissions are checked again on every single request, not just at sign-in. Remove someone's access in the panel and the connection they approved loses it immediately.
These questions use the available tools. Sales questions need reports.view; order lists need orders.view. Comparisons require separate dated queries, and lowest-selling lists exclude dishes with no sales.
Needs: reports.view, orders.view
Reading lists: menu-items.view. Saving descriptions or availability: menu-items.edit; changes publish immediately.
Profile reads and readiness checks: settings.view. Profile and FAQ saves: settings.edit; changes publish immediately.
Needs: employees.view
Twelve tools exist in the restaurant connector at api.rosuii.com/v1/mcp. A connection is offered only the tools the approving user may already use in the panel. Permissions are checked again on each call; assigned-branch restrictions also apply.
Permission identifiers are shown exactly as used by the panel. Scroll the table horizontally on a small screen; keyboard users can focus the table region and use the arrow keys.
| Tool | What it does | Required panel permission |
|---|---|---|
get_my_restaurant | Get this restaurant's public profile | settings.view |
audit_growth | Audit online and AI visibility | settings.view |
list_menu_items | List menu items and their descriptions | menu-items.view |
update_menu_item_description | Save a menu item description | menu-items.edit |
update_seo_profile | Save public profile and SEO fields | settings.edit |
list_branches | List this restaurant's branches | menu-items.view |
set_menu_item_branch_availability | Turn a dish on or off at one branch | menu-items.edit |
publish_faq | Publish a question and answer to the website | settings.edit |
list_orders | List recent orders | orders.view |
get_sales_summary | Sales and revenue for a date range | reports.view |
get_top_items | Best and worst selling dishes | reports.view |
list_staff | List staff | employees.view |
No connection can take, void or refund a payment, change a price, create a staff login or change a plan.
This is not a public-data-only connection: permitted read tools can return orders, sales and staff records. The writing tools can save descriptions and public profile fields, publish an answer or change a dish’s availability at a branch. Review those changes before asking the assistant to save them.
These are not warnings about misuse. The tools simply do not exist in the connector, so no assistant can be talked into them.
The connection is useful on the day you make it, but the bigger gain is what becomes easy enough to actually do often.
A name such as Set Menu 3 leaves the meal unclear. Give the assistant confirmed ingredients and portions, review its wording, then ask to save. The description becomes public immediately; clearer content does not guarantee a recommendation.
Parking, home delivery area, whether you take card, how many people the party room seats. Publish only confirmed answers so guests can read the information. Saving a FAQ makes it public immediately.
Use a compatible assistant with internet access to ask for dated sales and dish quantities. Compare the answer with your reports: the summary’s collected field counts fully paid bills, not partial receipts or a reconciled cash drawer.
With menu editing permission, specify a dish and branch to switch availability. The public menu changes immediately. There is no expiry schedule: explicitly switch it back on when ready.
Every Rosuii storefront is published so assistants can read it, and the audit tool tells you what is still missing. No one can promise you a ranking in ChatGPT or Google's AI answers, and anybody who does is selling something. What is in your control is being complete and readable, and this tells you how close you are.
The things worth knowing before you connect anything to anything.
No. You add the Rosuii address in ChatGPT or Claude, sign in to Rosuii the same way you sign in to the panel, and press approve. There is no key to copy, no developer account and nothing to install.
Yes. You ask in Bangla and the assistant answers in Bangla. The assistant handles the language; Rosuii supplies your restaurant's data. Bangla and English both work, including a mix of the two.
Every Rosuii plan, including Free. The connector is not a paid Rosuii add-on; check the assistant provider’s own plan and connector requirements separately.
It can, if the account that approved it can. A connection approved by an owner can read orders, sales summaries and best-selling dishes. A connection approved by someone without report access cannot, because those tools are never offered to it.
No. Taking a payment, voiding one, refunding, changing a price, creating a staff login and changing your plan are all absent from the tool set. There is no wording that persuades an assistant into an action that does not exist.
Deactivate them in the panel as you normally would. Their connection stops working, because permissions are read from their live account on every request rather than stored when they approved.
An assistant is expected to show you wording before saving, and that is how the flow is meant to be used. The honest caution is that the assistant, not Rosuii, controls that conversation: ask it to show you the text first, and read it before you say yes, because a save is live on your public website straight away.
No. Rosuii runs no language model of its own. ChatGPT or Claude writes the words and Rosuii stores what you approve. The menu and category quick-add tools inside the panel are a different thing: they fill from prepared Bangladeshi presets, not from a language model.
Yes. Turning a dish on or off is a per-branch action, and someone assigned to a single branch can only do it at that branch — another branch is refused. What is not branch-specific is restaurant-level content: a menu description, the public profile and the website FAQ belong to the whole restaurant, so an edit there applies everywhere and publishes immediately.
Nobody can promise that, and Rosuii does not. No assistant is obliged to mention any restaurant. What you can control is being complete and readable — published dishes, real descriptions, answered questions — and the audit tool in the connector tells you what is still missing.
Remove the connector in ChatGPT or Claude. To stop it from the Rosuii side, change the approving user's permissions or deactivate the account; the connection loses the same access at the same moment.
The connector follows the Model Context Protocol and signs in with standard OAuth, so an assistant that supports both can connect. Check the actual client’s connector support before relying on it.
Create a free Rosuii account, add your menu, and connect it to the assistant you already use. The questions in this page are the ones to start with.
Page reviewed: