Summary
iiko and Syrve restaurant management through the iikoCloud API (Syrve Cloud API): organizations and terminal groups, menu and external menus, stop lists, delivery and table orders, reservations, couriers, order and payment types, discounts and loyalty customers. API login from the web back office.
Guided setup
Connect iiko to Claude in 2 minutes
Start a free trial on AnythingMCP Cloud, connect iiko in the guided setup, then add your MCP URL to Claude. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
AnythingMCP is listed in Claude's connector directory: add it to Claude in one click (opens in a new tab), then sign in and choose which MCP servers Claude may use.
Try asking
Example prompts for iiko
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → iiko, paste the API login and pick iiko or Syrve for the API host and the loyalty paths, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
iiko + Claude
iiko and Syrve restaurant management through the iikoCloud API (Syrve Cloud API): organizations and terminal groups, menu and external menus, stop lists, delivery and table orders, reservations, couriers, order and payment types, discounts and loyalty customers. API login from the web back office.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
IIKO_API_HOST, IIKO_LOYALTY_API, IIKO_API_LOGIN
Step 1 — Get credentials
Setting up takes about 5 minutes.
- Sign in to the web back office (iikoWeb for iiko, Syrve Web / Syrve App for Syrve) as an administrator and open the cloud API settings (Integrations, API keys; called API settings or Live API settings in older versions).
- Create an API login (API key) for this connector: give it a name, pick the organizations it may reach and an expiry date (at most 2 years). Copy the key; a new key is 36 characters long and may be shown only once.
- Paste it into
IIKO_API_LOGIN. Pick your product twice: the API host inIIKO_API_HOSTand the same product inIIKO_LOYALTY_API(iiko and Syrve name the loyalty paths differently). - Optional: put the id of your main restaurant into
IIKO_ORGANIZATION_IDafter the firstiiko_list_organizationscall, so tools that take one organization can leave it out.
The connector exchanges the API login at /api/1/access_token for a bearer token that lasts 1 hour and renews it by itself. iiko marks this login call as deprecated in favour of /api/v2/access_token, which also needs an app registered in the developer portal; if iiko switches the old call off, the setup check reports a failed login.
Where to start: iiko_list_organizations gives the organization ids every other tool needs. iiko_list_terminal_groups lists the POS installations of an organization and iiko_check_terminal_groups_alive tells whether they are online.
Menu: iiko_list_external_menus and iiko_get_external_menu read the menus prepared for delivery channels, with prices per organization. iiko_get_nomenclature reads the full back office menu (large; documented for Syrve, no longer in the iiko reference, so prefer the external menu on iiko). iiko_get_stop_lists shows what is out of stock per terminal group; iiko_add_to_stop_list and iiko_remove_from_stop_list change it and are installed switched off (they need an API login with the extra stop-list right).
Delivery orders: iiko_list_deliveries_by_date_and_status (the daily overview), iiko_search_deliveries (text search and problem filter), iiko_list_deliveries_by_phone, iiko_get_deliveries_by_id. These are guaranteed for the last 7 days; iiko_list_delivery_history_by_phone reaches back 90 days. Statuses: Unconfirmed, WaitCooking, ReadyForCooking, CookingStarted, CookingCompleted, Waiting, OnWay, Delivered, Closed, Cancelled. iiko_create_delivery and iiko_cancel_delivery are installed switched off: a created order reaches the kitchen and a cancellation cannot be undone.
Table orders and reservations: iiko_get_table_orders_by_id and iiko_list_table_orders_by_table read dine-in orders. For reservations, iiko_list_reserve_terminal_groups, then iiko_list_restaurant_sections (halls and tables), iiko_list_reserves (what is booked from a time on) and iiko_get_reserves_by_id (the details). The connector does not create reservations.
Dictionaries: iiko_list_order_types, iiko_list_payment_types, iiko_list_discounts, iiko_list_cancel_causes, iiko_list_couriers. They rarely change: read them once per conversation, not per order.
Loyalty: iiko_get_customer finds a guest by phone, email or card and shows the wallet balances; iiko_list_customer_transactions lists the bonus movements; iiko_list_customer_categories and iiko_list_loyalty_programs describe the programme. iiko_create_or_update_customer saves guest master data. The connector never tops up, holds or writes off a wallet and records no payments.
Commands: creating or cancelling a delivery and changing a stop list answer at once with a correlationId; the POS carries the command out afterwards. Read the outcome with iiko_get_command_status (InProgress, Success, Error).
Formats: ids are UUIDs. Dates are yyyy-MM-dd HH:mm:ss.fff without a time zone: order and reservation times are local to the terminal (see the time zone in iiko_list_terminal_groups), loyalty report dates are UTC. Sums are in the currency of the organization. Almost every call is a POST with a JSON body, also the reads.
Limits: iiko groups the methods (dictionaries, menu, stop lists, order reading and others) and limits each group per time slot, usually one minute; over the limit every call of that group answers 429 until the slot ends. Limits for order and stop-list methods grow with the number of restaurants. Ask for several organizations in one call instead of one call each, cache dictionaries and menus, and do not poll single orders. Repeating identical or failing requests in bulk can get the API login blocked.
Errors: an error answer has errorDescription and often error (a code) plus a correlationId to quote to iiko support. 401 means the token or API login was refused, 400 names the wrong field, 408 means the POS did not answer in time (the restaurant may be offline).
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Claude
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Recommended path: works on claude.ai web without editing any config file.
- In Claude, open Plugins (still called Customize on some plans) → Connectors.
- Click + Add, then Add custom connector.
- Enter a name, e.g.
iiko, and the remote MCP server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Continue, keep the detected settings and click Continue again. - Choose Sign in now, click Add and sign in to AnythingMCP (OAuth) to allow access.
All tools below appear in your chat: start typing prompts.
Available tools
| Tool | What it does |
|---|---|
iiko_list_organizations | List the organizations (restaurants) the API login can reach: id, name and code, plus country, address, coordinates, time zone settings… |
iiko_list_terminal_groups | List the terminal groups (the POS installations orders are sent to) of one or more organizations: per organization the groups with id… |
iiko_check_terminal_groups_alive | Check whether terminal groups are online right now: per terminal group isAlive true or false. Use it before telling someone a restaurant… |
iiko_get_nomenclature | Read the full menu (nomenclature) of one organization as exported from the back office: groups, product categories, products (dishes… |
iiko_list_external_menus | List the external menus (the menus prepared for delivery sites and apps in the web back office) and the price categories of the account: id… |
iiko_get_external_menu | Read one external menu with its item categories, items, sizes, prices per organization, modifier groups, allergens, nutrition values… |
iiko_get_stop_lists | Read the stop lists (out-of-stock items): per organization and terminal group the items with productId, sizeId, sku, balance (remaining… |
iiko_list_order_types | List the order types per organization: id, name, orderServiceType (Common for table orders, DeliveryByCourier, DeliveryByClient for… |
iiko_list_payment_types | List the payment types: id, code, name, paymentTypeKind (Cash, Card, External, LoyaltyCard and others), paymentProcessingType, the terminal… |
iiko_list_discounts | List the discounts and surcharges set up in the back office per organization: id, name, percent or fixed sum, mode, minimum order sum… |
iiko_list_cancel_causes | List the delivery cancellation causes: id, name and isDeleted. An id is needed to cancel a delivery. Read-only; cache the answer |
iiko_list_deliveries_by_date_and_status | List delivery and pickup orders by delivery date and status: per organization the orders with id, posId, creationStatus and the order… |
iiko_list_deliveries_by_phone | Find the recent delivery orders of a phone number (guaranteed for the last 7 days): the same order details as… |
iiko_list_delivery_history_by_phone | Find older delivery orders of a phone number in the order history (kept 90 days): the same order details, grouped by organization, at most… |
iiko_search_deliveries | Search delivery orders by text (prefix search on order number, customer name, phone or address) with filters for date, status, service type… |
iiko_get_deliveries_by_id | Read up to 200 delivery orders by id: creationStatus (Success, InProgress, Error with errorInfo) and the full order with status, customer… |
iiko_get_table_orders_by_id | Read table (dine-in) orders by id: creationStatus and the order with tableIds, status (New, Bill, Closed, Deleted), waiter, customer… |
iiko_list_table_orders_by_table | List the table (dine-in) orders of given tables, optionally by status and creation date: the same details as iiko_get_table_orders_by_id.… |
iiko_list_reserve_terminal_groups | List the terminal groups of the given organizations that accept table reservations and banquets: id, name, address and time zone, and the… |
iiko_list_restaurant_sections | List the restaurant sections (halls) of terminal groups that accept reservations, with their tables: section id and name, and per table id… |
iiko_list_reserves | List the reservations and banquets booked in restaurant sections from a start time: id, tableIds, estimatedStartTime, durationInMinutes and… |
iiko_get_reserves_by_id | Read reservations and banquets by id: creationStatus, isDeleted and the reserve with customer, phone, guest count, tables, estimated start… |
iiko_list_couriers | List the employees who are delivery couriers, per organization: id, firstName, lastName, displayName, code and isDeleted. Read-only |
iiko_get_customer | Look up one loyalty customer (guest) by phone, email, card number, card track or id: id, name, surname, phone, email, birthday, sex… |
iiko_list_customer_categories | List the customer (guest) categories of the loyalty programme of an organization: id, name, isActive and isDefaultForNewGuests. Read-only |
iiko_list_loyalty_programs | List the loyalty programmes of an organization: id, name, description, programType, isActive, validity dates, walletId, and the marketing… |
iiko_list_customer_transactions | List the loyalty transactions of one customer in a period (bonus accruals and write-offs, wallet refills, coupons): type, typeName, sum… |
iiko_create_or_update_customer | Create a loyalty customer or update one found by id, phone or card: name, phone, email, birthday, sex, comment, consent status and… |
iiko_get_command_status | Check the result of a command (creating or cancelling a delivery, changing a stop list): state InProgress, Success or Error with… |
iiko_create_delivery | Create a delivery or pickup order in the POS. It is a command: the answer carries a correlationId and orderInfo with creationStatus… |
iiko_cancel_delivery | Cancel a delivery order, with a cancel cause. It cannot be undone and items already printed are written off. It is a command: check the… |
iiko_add_to_stop_list | Put products on the stop list of one terminal group, with the remaining quantity (0 for sold out). Guests can no longer order a sold-out… |
iiko_remove_from_stop_list | Take products off the stop list of one terminal group, so they can be ordered again. Needs an API login with the extra right to change stop… |
Example prompts
- "Which delivery orders from today are still not on their way, per restaurant?"
- "What is on the stop list at each terminal group right now?"
- "Are all our POS terminal groups online?"
- "Show the reservations for tonight from 18:00 at the main restaurant, with hall and table."
- "Find the guest with phone 79161234567 and show the bonus balance and last transactions."
FAQ
Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
Where does the API login come from? An administrator signs in to the web back office (iikoWeb for iiko, Syrve Web for Syrve) and opens Integrations, API keys (API settings in older versions). Create an API login for the connector, pick the organizations it may reach and an expiry date of at most 2 years, and copy the key. Then pick your product for the API host and the loyalty paths: iiko uses api-ru.iiko.services, Syrve uses api-eu.syrve.live, and a key only works on its own product's host.
What does it cover? Organizations and terminal groups with their online status, the external menus with prices and the back office menu, stop lists, delivery orders by date, status, phone or text search, table orders, reservations with halls and tables, couriers, order and payment types, discounts and cancel causes, and loyalty guests with wallet balances and bonus transactions. It saves guest master data, but it never tops up, holds or writes off a wallet, records no payments and creates no reservations.
Which tools install switched off? iiko_create_delivery, iiko_cancel_delivery, iiko_add_to_stop_list and iiko_remove_from_stop_list. A created order goes straight to the kitchen and a cancellation cannot be undone, and the stop-list tools need an API login with the extra stop-list right. Switch them on on the connector page only if the AI should use them.
Next steps
- Connector landing page
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
- Connect to Microsoft Copilot
Was this guide helpful?