iikoServer MCP
Exposes iiko restaurant management system REST API as 42+ LLM-callable tools over stdio, enabling natural language interaction with products, employees, orders, payments, OLAP reports, and assembly charts.
README
iikoServer MCP Server
MCP (Model Context Protocol) server exposing the iiko restaurant management system REST API as 42+ LLM-callable tools over stdio.
Features
- 42+ tools — products, employees, orders, payments, OLAP reports, assembly charts
- Auto-auth — SHA1 password hashing + session cookie, re-authenticates on 401
- Graceful shutdown — sends logout to release iiko license slot
- Self-signed cert support —
IIKO_VERIFY_SSL=falseby default - Venue mapping — optional
IIKO_VENUE_MAPto tag cash register numbers with names - Business-level helpers —
get_checks,get_venues_revenue,get_staff_meals,get_top_dishes,compare_revenue - Docker-ready — Python 3.12-slim, stdio protocol
Quick Start
Local (pip)
git clone https://github.com/your-org/iiko-server-mcp.git
cd iiko-server-mcp
pip install -r requirements.txt
IIKO_URL=https://your-restaurant.iiko.it:443 \
IIKO_LOGIN=your_login \
IIKO_PASS=your_password \
python3 server.py
Docker
docker build -t iiko-server-mcp .
docker run -i --rm \
-e IIKO_URL=https://your-restaurant.iiko.it:443 \
-e IIKO_LOGIN=your_login \
-e IIKO_PASS=your_password \
iiko-server-mcp
Important: MCP servers use stdio (not HTTP). The container must run with -i (interactive) so the MCP client can communicate via stdin/stdout. Do not use -d (detached).
Configuration
Copy .env.example to .env and fill in real values:
| Variable | Required | Default | Description |
|---|---|---|---|
IIKO_URL |
yes | — | iikoServer base URL, e.g. https://my-restaurant.iiko.it:443 |
IIKO_LOGIN |
yes | — | Login username |
IIKO_PASS |
yes | — | Plain password (SHA1-hashed before sending) |
IIKO_VENUE_MAP |
no | — | "Venue A=4,Venue B=5" — names for cash register numbers |
IIKO_VERIFY_SSL |
no | false |
Set to true if using a CA-signed certificate |
MCP Client Configuration
Hermes Agent
# ~/.hermes/config.yaml
mcp_servers:
iiko-server:
command: python3
args: ["/path/to/iiko-server-mcp/server.py"]
env:
IIKO_URL: "https://your-restaurant.iiko.it:443"
IIKO_LOGIN: "your_login"
IIKO_PASS: "your_password"
IIKO_VENUE_MAP: "Cafe A=4,Cafe B=5"
For Docker:
mcp_servers:
iiko-server:
command: docker
args: ["run", "-i", "--rm",
"-e", "IIKO_URL=https://your-restaurant.iiko.it:443",
"-e", "IIKO_LOGIN=your_login",
"-e", "IIKO_PASS=your_password",
"iiko-server-mcp"]
Claude Desktop
{
"mcpServers": {
"iiko-server": {
"command": "python3",
"args": ["/path/to/iiko-server-mcp/server.py"],
"env": {
"IIKO_URL": "https://your-restaurant.iiko.it:443",
"IIKO_LOGIN": "your_login",
"IIKO_PASS": "your_password"
}
}
}
}
Cursor
{
"mcpServers": {
"iiko-server": {
"command": "python3",
"args": ["/path/to/iiko-server-mcp/server.py"],
"env": {
"IIKO_URL": "https://your-restaurant.iiko.it:443",
"IIKO_LOGIN": "your_login",
"IIKO_PASS": "your_password"
}
}
}
}
Available Tools
System
- ping — Health check, server URL + auth state
- list_endpoints — All 42 tools with descriptions
Products / Nomenclature
- get_products / get_nomenclature — All products
- get_product_groups — Product categories with hierarchy
- get_product_sizes — Sizes/units
- get_corporate_structure — Departments structure
- get_corporate_groups — Corporate groups
- search_products — Substring search by name
Employees
- get_employees / get_employee / get_employee_roles / get_persons
Entities
- get_entity_types / get_entities / get_entity_by_id
- get_stores — Warehouses
- get_contractors — Suppliers
Documents
- get_incoming_invoices / get_outgoing_invoices — by date range (DD.MM.YYYY)
- get_incoming_invoice_by_id / get_outgoing_invoice_by_id
- get_waste_documents — Write-off documents
- get_menu_changes / get_menu_change_by_id
Recipes (Assembly Charts)
- get_assembly_charts — All tech cards
- get_assembly_chart_by_id — Single chart
- save_assembly_chart — Create/update (⚠️ modifies production data)
Cash & Payments
- get_payment_types
- get_cash_shifts / get_cash_shift — by session UUID
- get_payments / get_payment — per session
- create_encashment — Cash in/out (⚠️ modifies production data)
Prices
- get_price_categories / get_price_category
Reports & OLAP
- get_olap_columns — Schema for a report type (e.g.
SALES) - run_olap_report — Raw OLAP with custom columns/filters (DD.MM.YYYY)
- get_olap_presets / run_olap_by_preset — Saved presets
- run_custom_report — Named custom reports (DD.MM.YYYY)
- get_venues_revenue — Daily revenue by venue (YYYY-MM-DD)
- get_staff_meals — Free staff meals per venue (YYYY-MM-DD)
- get_top_dishes — Top N dishes by revenue (YYYY-MM-DD)
- compare_revenue — Day-over-day revenue comparison
- get_checks — Individual orders with payment type & masked card (YYYY-MM-DD)
Raw
- raw_request — Direct authenticated HTTP call to any iikoServer endpoint
Date Format
| Tool Group | Format | Example |
|---|---|---|
Business helpers (get_venues_revenue, get_checks, etc.) |
YYYY-MM-DD | 2026-07-17 |
Legacy OLAP (run_olap_report, run_olap_by_preset) |
DD.MM.YYYY | 17.07.2026 |
All business tools default to Moscow time (UTC+3) if no date is provided.
Known Limitations
get_cash_shifts— requires a date parameter; currently returns 409 if called without oneget_payment_types— returns 404 on some iikoServer versions (endpoint may not exist)- Staff meal detection — filters by
"(без оплаты)"payment type label; verify this matches your iiko configuration CardTypeName— may return"(нет карты)"depending on acquirer integration- Self-signed certs — default
verify=False; setIIKO_VERIFY_SSL=truefor CA-signed certificates
Development
# Syntax check
python3 -m py_compile server.py
# Run locally with test env
IIKO_URL=... IIKO_LOGIN=... IIKO_PASS=... python3 server.py
# Build Docker
docker build -t iiko-server-mcp .
Adding a Tool
- Write a handler with the
@tool("name", "description", input_schema)decorator - Add
"name"to the appropriate category inENDPOINT_CATALOG - Python will auto-register it — no other wiring needed
License
MIT — see LICENSE
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。