Local services & SaaS
TMBill
Outlet reports, inventory and staff from the TMBill restaurant backoffice.
3 endpoints
The official eZee Optimus API reads F&B purchase, sales and account data, with no endpoint for orders or bills and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted eZee Optimus MCP server with 8 tools that ChatGPT and Claude use in your own restaurant login. Anything that reaches the kitchen, a printer or a guest's bill waits for your OK.
8 tools Read and write
eZee Optimus documents a Connectivity API on the eZee Connectivity Portal with three read endpoints: F&B purchases, F&B sales and financial accounts. No endpoint for orders, kitchen tickets or bills was found, and no eZee Optimus MCP server or official ChatGPT or Claude connector was verified.
| What you need | Connectivity API | RapidServe | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server verified | A waiter taps it in | Hosted MCP server |
| Enter dine-in and takeaway orders | No order endpoint found | On a phone or tablet | After your OK |
| Print KOTs, split and settle bills | Not in the API | On a phone or tablet | 8 tools, writes ask first |
| Run from n8n or a script | Finance reads, your code | Manual only | REST, same key |
Checked 15 Nov 2026. Sources: eZee Connectivity Portal: eZee Optimus · eZee Optimus web login (knowledge base) · RapidServe - eZee Optimus (App Store) · RapidServe - eZee Optimus (Google Play)
Once, in a browser we host for you.
One address in its settings.
Read out a pickup, then approve the ticket.
Your agent works in your own signed-in Cloud Browser. Orders, tickets, discounts and bills wait for your OK. Who can see your session
Sign in to eZee Optimus in a Cloud Browser. Open app.ipos247.com in your Cotlet Cloud Browser, enter your user name, password and restaurant code, then pick your terminal and outlet.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
eZee Optimus shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector covers them all. Added eZee Optimus after connecting? Refresh the connector and its 8 tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: ezee_optimus_read One tool per order and bill action the vendor lists for eZee Optimus. The order list only reads; every tool that changes an order, prints or touches a bill asks first, except guest details on a table.
Find an order, seat the guest, send a table to the kitchen or enter a pickup. Most other tools take an order from the list.
Returns each order with its table or takeaway guest, its status and its amount, as your signed-in user sees them in the outlet you chose at sign-in. Most write tools take an order from this list, so it is usually the first call. It changes nothing and runs without asking.
MCP callezee_optimus_read → filter_restaurant_orders
REST endpointGET https://cotlet.dev/api/v1/ezee-optimus/restaurant-orders/filter
| Name | Type | Description |
|---|---|---|
| order_type string | string | One of `dine_in`, `takeaway`, `all`. Defaults to `all`. |
| table string | string | Only the orders of this table, by the name your floor plan uses. |
| date string | string | ISO date. Defaults to today. |
{
"date": "2026-11-15",
"orders": [
{
"order": "Window table",
"type": "dine_in",
"status": "Open",
"amount": 86.4
},
{
"order": "Pickup for Lee",
"type": "takeaway",
"status": "Ready",
"amount": 42.1
},
{
"order": "Terrace table",
"type": "dine_in",
"status": "Settled",
"amount": 124.5
}
]
} This keeps the right guest on the right table, which eZee Optimus uses to keep orders accurate. It reaches no one and is put right by calling it again with the earlier details, so it runs without asking.
MCP callezee_optimus_write → record_table_guest_info
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/table-guest-infos
| Name | Type | Description |
|---|---|---|
| table string required | string | The table to update. |
| guest object required | object | The guest information eZee Optimus asks for at the table, as you give it. |
{
"table": "table",
"guest": "guest"
} {
"table": "Window table",
"guest": {
"name": "Example Guest"
},
"saved": true
} eZee Optimus passes the order to the kitchen, so your cooks start on it as soon as it is sent. The agent reads the table and every item back to you before it goes. Print the kitchen order ticket with print_receipts_and_kots if your kitchen works from paper. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → send_orders_to_kitchen
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/orders-to-kitchens
| Name | Type | Description |
|---|---|---|
| table string required | string | The table the order is for. |
| items array required | array | Menu items by the name on your eZee Optimus menu, each with a quantity and an optional note for the kitchen. |
{
"table": "table",
"items": "items"
} {
"order": "Window table",
"type": "dine_in",
"items": [
{
"item": "Paneer tikka",
"quantity": 2
},
{
"item": "Garlic naan",
"quantity": 3
}
],
"sent_to_kitchen": true
} The order joins the takeaway orders in eZee Optimus next to the ones your counter staff enter, and the kitchen works from it. The agent shows you the guest and the items before it saves. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → create_takeaway_orders
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/takeaway-orders
| Name | Type | Description |
|---|---|---|
| guest string required | string | Who collects the order, as you want it on the ticket. |
| items array required | array | Menu items by the name on your eZee Optimus menu, each with a quantity and an optional note for the kitchen. |
{
"guest": "Pickup for Lee",
"items": [
{
"item": "Butter chicken",
"quantity": 2
},
{
"item": "Jeera rice",
"quantity": 2,
"note": "Pickup at 7 pm"
}
]
} {
"order": "Pickup for Lee",
"type": "takeaway",
"items": [
{
"item": "Butter chicken",
"quantity": 2
},
{
"item": "Jeera rice",
"quantity": 2
}
],
"amount": 42.1,
"saved": true
} Items in and out, extra charges and an order-level discount. Each changes what the guest pays.
Changes the order and what the guest pays, so the agent shows you the order before and after. It works on items in an order; it does not change your menu setup. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → update_order_items
REST endpointPATCH https://cotlet.dev/api/v1/ezee-optimus/order-items
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, by table or order number as filter_restaurant_orders returns it. |
| action string required | string | One of `add`, `update`, `remove`, `extra_charge`. |
| items array | array | For `add`, `update` and `remove`: the menu items and quantities. |
| charge object | object | For `extra_charge`: the charge as eZee Optimus lists it, and its amount. |
{
"order": "order",
"action": "action"
} {
"order": "Window table",
"removed": [
{
"item": "Garlic naan",
"quantity": 1
}
],
"amount": 82.9,
"saved": true
} The discount is at order level, as eZee Optimus applies it, and lowers what the guest pays, so it waits for your OK with the old and new totals side by side. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → apply_order_discounts
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/order-discounts/apply
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, by table or order number as filter_restaurant_orders returns it. |
| discount string required | string | The discount: a percentage or an amount, or one set up in eZee Optimus, by name. |
| reason string | string | Why, for your own records. |
{
"order": "order",
"discount": "discount"
} {
"order": "Terrace table",
"discount": "10%",
"amount_before": 138.33,
"amount": 124.5,
"saved": true
} Paper for the kitchen and the guest, then the bill: split it, then settle it in a separate call.
Prints on the printers your eZee Optimus outlet already uses, so paper comes out in your restaurant. The agent names the order and the document first. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → print_receipts_and_kots
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/receipts-and-kots/print
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, by table or order number as filter_restaurant_orders returns it. |
| document string required | string | One of `receipt`, `order`, `kot`. |
{
"order": "order",
"document": "document"
} {
"order": "Pickup for Lee",
"document": "kot",
"printed": true
} Splitting and settling are separate calls, so you can read the split before the bill is closed. A settled bill is money taken: the agent states the order, the amount and the payment before it settles. By default you confirm each call; you can switch that off for this tool.
MCP callezee_optimus_write → settle_or_split_bills
REST endpointPOST https://cotlet.dev/api/v1/ezee-optimus/or-split-bills/settle
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, by table or order number as filter_restaurant_orders returns it. |
| action string required | string | One of `split`, `settle`. |
| parts array | array | For `split`: the items or amounts each part of the bill takes. |
| payment string | string | For `settle`: how the guest paid, from the payment types set up in your eZee Optimus. |
{
"order": "order",
"action": "action"
} {
"order": "Terrace table",
"parts": [
{
"part": 1,
"amount": 62.25
},
{
"part": 2,
"amount": 62.25
}
],
"settled": false
} Your signed-in eZee Optimus browser profile, AES-256-GCM encrypted, in Finland. Never your password or PIN.
The 8 eZee Optimus tools. The session cookie stays in the Cloud Browser.
The orders and bills of the outlet you picked at sign-in, as far as your eZee Optimus user can open them.
eZee Optimus users and PIN login settings, your menu setup and your outlet settings.
You sign in again yourself, in the same Cloud Browser.
Disable eZee Optimus for agents, reset the browser, or change your eZee Optimus password.
You type your user name, password and restaurant code yourself; the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the eZee Optimus server when the web POS changes its order and bill screens, so your agent keeps working without a code change on your side.
The agent works in one outlet at a time: the one you chose after the restaurant code. A user with fewer rights in eZee Optimus gives the agent fewer orders and bills to work on.
Cotlet never sees or stores your password. If eZee Optimus signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Guest details on a table | Call record_table_guest_info again with the right details |
| Items, extra charges or a discount on an open order | Change them back with update_order_items or apply_order_discounts before the bill is settled |
| Order sent to the kitchen | Your cooks may have started: tell the kitchen directly |
| Printed KOT or receipt | The paper is out: reprint the right one |
| Settled bill | The money is taken: handle it in eZee Optimus the way your restaurant handles a wrong bill |
6 of the 7 write tools ask first: by default you confirm each call, and you can switch that off per tool. Guest details on a table and the order list run at once.
{
"name": "create_takeaway_orders",
"arguments": {
"guest": "Pickup for Lee",
"items": [
{
"item": "Butter chicken",
"quantity": 2
},
{
"item": "Jeera rice",
"quantity": 2,
"note": "Pickup at 7 pm"
}
]
}
} curl -X POST https://cotlet.dev/api/v1/ezee-optimus/takeaway-orders \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"guest":"Pickup for Lee","items":[{"item":"Butter chicken","quantity":2},{"item":"Jeera rice","quantity":2,"note":"Pickup at 7 pm"}]}' {
"order": "Pickup for Lee",
"type": "takeaway",
"items": [
{
"item": "Butter chicken",
"quantity": 2
},
{
"item": "Jeera rice",
"quantity": 2
}
],
"amount": 42.1,
"saved": true
} The example enters Lee's pickup, two butter chicken and two jeera rice, as one takeaway order of 42.10 in your menu prices. A cron job or n8n flow can make the same call over REST at /api/v1/ezee-optimus with the same key and price, in JSON. Failed calls are free.
About $28 a monthfor one outlet that takes phone and chat pickups, 4,900 credits. Your eZee Optimus plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Phone and chat takeaway orders, with the KOT | 2 × 120 | 2,400 |
| Order corrections and discounts | 2 × 20 | 400 |
| Split bills and their receipts | 2 × 15 | 300 |
| Open orders check before closing | 1 × 30 | 300 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 340 calls | 4,900 |
The smallest pack, 5,000 credits for $29, covers this month. A busier outlet with more pickups uses more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Connectivity API | Reads F&B purchases, F&B sales and financial accounts for a date range, for your own code. | No order, ticket or bill endpoint found; you write, host and fix the client. |
| RapidServe | The vendor's free waiter app: takes orders, prints KOTs, splits and settles bills. | A person taps every order in on a phone or tablet. |
| By hand | Sign in to the web POS and work each order. | One order at a time, only while someone is at the screen. |
For sales and purchase figures in your accounts, the Connectivity API is the vendor's own route: use it. Cotlet fits when you want ChatGPT, Claude or a script to enter orders, print tickets and split bills in eZee Optimus today, from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the eZee Optimus tools.
Sign up free at https://cotlet.dev/signup?app=ezee-optimus, turn on eZee Optimus under Integrations in the console and sign in at https://app.ipos247.com/ in your Cloud Browser. Then connect your AI agent and ask it for today's orders. The trial needs no card.
eZee Optimus has an official Connectivity API for finance data: it documents three read endpoints, for F&B purchases, F&B sales and financial accounts (checked 15 Nov 2026). No endpoint for taking orders, sending them to the kitchen or settling bills was found, and no eZee Optimus MCP server or official ChatGPT or Claude connector was verified. Cotlet does not use that API: it works in your own signed-in eZee Optimus account.
No. RapidServe is the free ordering app eZee Optimus offers for waiters on iPhone and Android; its orders sync to eZee Optimus. Cotlet works in the eZee Optimus web login instead, so ChatGPT, Claude or a script can enter and change orders from anywhere.
The web login at app.ipos247.com: user name, password and restaurant code, then the terminal and outlet, as the eZee Optimus knowledge base describes it. You sign in yourself once; the agent works in the outlet you picked.
It works in the outlet you picked when you signed in. For another outlet, sign in again in the same Cloud Browser and pick that outlet.
Only in how it is called. Both carry the same 8 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with eZee Optimus or Yanolja Cloud Solution.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy