eZee Optimus API and MCP server Let your AI agent take the order and split the bill.

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.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with eZee Optimus
eZee Optimus logo eZee Optimus Cloud Browser

8 tools Read and write

Restaurant orders and bills

What can your AI agent do in eZee Optimus? The order and bill work around the floor and the counter.

  • Turn a phoned pickup into a takeaway order

  • Send a table order to the kitchen

  • Print the KOT or the receipt

  • Fix the items on an open order

  • Split a table bill between guests

  • List the orders still open at closing

API reads finance data

Does eZee Optimus have an MCP server or an API? The official eZee Optimus routes, checked 15 November 2026.

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.

  • The three endpoints live at api.ipos247.com/v1/fas and take a hotel code and a date range, with Basic authentication.
  • RapidServe is the vendor's own free ordering app for waiters on iPhone and Android; its orders sync to eZee Optimus.
  • The web login at app.ipos247.com asks for a user name, password and restaurant code, then a terminal and outlet.
The eZee Optimus API, RapidServe and Cotlet compared
What you need Connectivity APIRapidServeCotlet
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)

Set up once

How does the eZee Optimus MCP server work? The eZee Optimus MCP server by Cotlet: your agent works in your own restaurant login.

  1. 1Sign in to eZee Optimus

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the orders

    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

Any MCP client

How to connect eZee Optimus to your AI agent

  1. 1

    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.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    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.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude
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
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: ezee_optimus_read
1 read, 7 write

All 8 eZee Optimus MCP tools

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.

Orders: dine-in and takeaway4

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.

  • filter_restaurant_orders List the orders in eZee Optimus, filtered by type, table or date. read

    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

    Parameters

    Parameters: filter_restaurant_orders
    NameTypeDescription
    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.

    Example response

    {
      "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
        }
      ]
    }
  • record_table_guest_info Add or correct the guest information on a dine-in table. write

    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

    Parameters

    Parameters: record_table_guest_info
    NameTypeDescription
    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.

    Example input

    {
      "table": "table",
      "guest": "guest"
    }

    Example response

    {
      "table": "Window table",
      "guest": {
        "name": "Example Guest"
      },
      "saved": true
    }
  • send_orders_to_kitchen Take a dine-in order for a table and send it to the kitchen. writeAsks first

    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

    Parameters

    Parameters: send_orders_to_kitchen
    NameTypeDescription
    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.

    Example input

    {
      "table": "table",
      "items": "items"
    }

    Example response

    {
      "order": "Window table",
      "type": "dine_in",
      "items": [
        {
          "item": "Paneer tikka",
          "quantity": 2
        },
        {
          "item": "Garlic naan",
          "quantity": 3
        }
      ],
      "sent_to_kitchen": true
    }
  • create_takeaway_orders Enter a takeaway order, for example one a guest phoned or messaged in. writeAsks first

    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

    Parameters

    Parameters: create_takeaway_orders
    NameTypeDescription
    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.

    Example input

    {
      "guest": "Pickup for Lee",
      "items": [
        {
          "item": "Butter chicken",
          "quantity": 2
        },
        {
          "item": "Jeera rice",
          "quantity": 2,
          "note": "Pickup at 7 pm"
        }
      ]
    }

    Example response

    {
      "order": "Pickup for Lee",
      "type": "takeaway",
      "items": [
        {
          "item": "Butter chicken",
          "quantity": 2
        },
        {
          "item": "Jeera rice",
          "quantity": 2
        }
      ],
      "amount": 42.1,
      "saved": true
    }

Changes to an open order2

Items in and out, extra charges and an order-level discount. Each changes what the guest pays.

  • update_order_items Add, change or remove menu items on an order, or add an extra charge. writeAsks first

    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

    Parameters

    Parameters: update_order_items
    NameTypeDescription
    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.

    Example input

    {
      "order": "order",
      "action": "action"
    }

    Example response

    {
      "order": "Window table",
      "removed": [
        {
          "item": "Garlic naan",
          "quantity": 1
        }
      ],
      "amount": 82.9,
      "saved": true
    }
  • apply_order_discounts Give a discount on a whole order. writeAsks first

    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

    Parameters

    Parameters: apply_order_discounts
    NameTypeDescription
    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.

    Example input

    {
      "order": "order",
      "discount": "discount"
    }

    Example response

    {
      "order": "Terrace table",
      "discount": "10%",
      "amount_before": 138.33,
      "amount": 124.5,
      "saved": true
    }

Tickets and bills2

Paper for the kitchen and the guest, then the bill: split it, then settle it in a separate call.

  • settle_or_split_bills Split an order's bill between guests, or settle it. writeAsks first

    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

    Parameters

    Parameters: settle_or_split_bills
    NameTypeDescription
    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.

    Example input

    {
      "order": "order",
      "action": "action"
    }

    Example response

    {
      "order": "Terrace table",
      "parts": [
        {
          "part": 1,
          "amount": 62.25
        },
        {
          "part": 2,
          "amount": 62.25
        }
      ],
      "settled": false
    }
Encrypted, revocable

Who can see my eZee Optimus session, and how do I revoke it?

  • What we store

    Your signed-in eZee Optimus browser profile, AES-256-GCM encrypted, in Finland. Never your password or PIN.

  • What your agent gets

    The 8 eZee Optimus tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The orders and bills of the outlet you picked at sign-in, as far as your eZee Optimus user can open them.

  • What no tool touches

    eZee Optimus users and PIN login settings, your menu setup and your outlet settings.

  • If eZee Optimus signs you out

    You sign in again yourself, in the same Cloud Browser.

  • How to cut access

    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).

We keep it working

What happens when eZee Optimus changes? The tools work through the same web POS your managers sign in to.

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.

6 tools ask first

Approvals, undo and mistakes Nothing reaches the kitchen, a printer or a bill until you say so.

  1. 01 Hear the order You pass on the guest and the items.
  2. 02 Show you the ticket Guest, items and amount, before saving.
  3. 03 Save after your OK create_takeaway_orders enters it.
  4. 04 Print the KOT print_receipts_and_kots, after a second OK.
Fixing an eZee Optimus write that went wrong
ActionHow to put it right
Guest details on a tableCall record_table_guest_info again with the right details
Items, extra charges or a discount on an open orderChange them back with update_order_items or apply_order_discounts before the bill is settled
Order sent to the kitchenYour cooks may have started: tell the kitchen directly
Printed KOT or receiptThe paper is out: reprint the right one
Settled billThe 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.

MCP call
{
  "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"
      }
    ]
  }
}
REST
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"}]}'
Response
{
  "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.

Pay per call

How much does the eZee Optimus MCP server cost?

About $28 a monthfor one outlet that takes phone and chat pickups, 4,900 credits. Your eZee Optimus plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Phone and chat takeaway orders, with the KOT2 × 1202,400
Order corrections and discounts2 × 20400
Split bills and their receipts2 × 15300
Open orders check before closing1 × 30300
Cloud Browser, 30 days1,500
Total340 calls4,900

The smallest pack, 5,000 credits for $29, covers this month. A busier outlet with more pickups uses more calls.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your eZee Optimus plan and user rights apply as they are

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

eZee Optimus MCP server: other ways to connect What each route does for a restaurant, and where it stops.

Other ways to work with eZee Optimus, checked 15 Nov 2026
OptionWhat it doesWhere it stops
Connectivity APIReads 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.
RapidServeThe 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 handSign 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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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.

eZee Optimus MCP server: questions

How do I get access?

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.

Does eZee Optimus have an API?

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.

Is this the same as RapidServe?

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.

Which eZee Optimus login does the agent use?

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.

Can the agent work in more than one outlet?

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.

Is the MCP server different from the REST API?

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.

Is Cotlet affiliated with eZee Optimus?

No. Cotlet is independent and not affiliated with eZee Optimus or Yanolja Cloud Solution.

Hand your next pickup order to your agent.

Free 7-day trial with 2,000 credits, no card needed.