iikoServer MCP: 39 iiko REST API tools
iikoServer MCP Server
An MCP server for the iikoServer REST API: products, employees, invoices, cash shifts, encashment and OLAP reports, including raw calls to any endpoint
- 1 ★ on the repository
- Last commit
Broad access
Why this level
- create_encashment writes a cash movement entry with no separate confirmation
- raw_request grants access to any iikoServer endpoint, including potentially data-changing ones
Install
- Works in
- Services
Manual install
pip install -r requirements.txtInstalling dependencies after cloning the repository.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- create_encashment writes a cash movement entry with no separate confirmation
- raw_request grants access to any iikoServer endpoint, including potentially data-changing ones
This is third-party code. Review the repository files before installing.
What it does
The server logs into iikoServer with a username and password (SHA1 is computed internally), automatically re-authenticates when the token expires, and logs out cleanly on shutdown to free the license slot. 39 tools are grouped by area: nomenclature and products, employees and roles, entities and warehouses, incoming and outgoing invoices, write-offs, menu changes, payment types, cash shifts and payments (including create_encashment for a cash-in/cash-out entry), price categories, and OLAP reports with custom columns and filters or saved presets. A separate raw_request tool lets you make any authorized call to iikoServer directly when no ready shortcut exists. All dates use the DD.MM.YYYY format iiko expects, and errors come back as a tool result rather than a server crash.
Who it is for. For restaurant owners and managers running iikoServer who want quick access to reports, nomenclature and cash data from an agent chat.
Good fit when
- You want to check revenue, stock, invoices or cash shifts for a period through an agent
- You need a custom OLAP report with specific columns and filters without opening the iiko interface
- You need access to an iikoServer endpoint with no ready-made tool yet, via raw_request
Not a fit when
- You don't want the agent able to create encashment entries: create_encashment writes a cash movement with no separate server-level confirmation
- You need a tool for iikoCloud or iikoTransport: this server is only for classic iikoServer
- You're not comfortable storing your iiko password in an environment variable: SHA1 is computed locally, but the plain password is still passed to the server
Example request
Show today's revenue as of 18:00 and the list of cash shifts for the weekMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
IIKO_URL- The iikoServer base URL, defaults to the author's demo address.
IIKO_LOGINrequired, secret- The iikoServer username.
IIKO_PASSrequired, secret- The user's password; SHA1 is computed by the server internally.
Limitations
The repository has no stated license. The raw_request and create_encashment tools run with no built-in server-level confirmation step; the risk of an erroneous call falls on the client and the user. The project comes from a single author, and the README doesn't describe a read-only versus write mode split. It accepts self-signed certificates without verification (verify=False), which weakens the connection if the iiko server itself is set up insecurely.
How to disable. Remove the iiko block from your MCP client configuration; the server logs out cleanly on normal process shutdown.
FAQ
Do I need to hash the password myself?
No, the server computes the SHA1 hash of the given password itself; IIKO_PASS takes the plain password.
What does raw_request do?
It makes any authorized call to iikoServer directly, useful for endpoints with no ready-made tool, but it needs to be used carefully.
Discussion
No questions or reviews yet.
Related
All iiko toolsiikoServer REST API MCP server: menu items, staff, invoices, cash shifts, OLAP reports and revenue by venue
A lightweight MCP server for manually debugging the iikoTransport API (api-ru.iiko.services) with v2 authorization and a universal arbitrary-request tool
An MCP server for the iikoCloud API: pick the needed subset from 236 methods by domain, defaults to read-only, confirms before every write
Multi-tenant Pyrus MCP server
Pyrus AI Ecosystem — MCP Infrastructure
An enterprise Pyrus v4 API MCP server with multi-tenancy, SQLite persistence and metrics, inside a larger monorepo
The Apideck MCP server: an agent works with over 200 business systems: accounting, HRIS, CRM and files through one unified API
Official Cybozu MCP server: an agent reads and changes kintone apps, records and spaces through the REST API.
README in short
The README lists 39 tools across eight sections: system, nomenclature, employees, entities, documents, cash and payments, prices, reports and OLAP, plus raw_request. It gives environment variables, configuration for Hermes Agent, Claude Desktop and Cursor, the DD.MM.YYYY date format, and a feature list: auto re-authentication, clean logout, self-signed certificate support, errors returned as tool results.