iiko-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IIKO_APP_ID | Yes | appId from the developer portal | |
| IIKO_BASE_URL | No | Optional. Base URL of the iikoTransport API. Defaults to https://api-ru.iiko.services | https://api-ru.iiko.services |
| IIKO_API_LOGIN | Yes | apiKey from iikoWeb | |
| IIKO_TIMEOUT_MS | No | Optional. Request timeout in milliseconds. Defaults to 30000 | 30000 |
| IIKO_CLIENT_SECRET | Yes | clientSecret from the developer portal (shown only once) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iiko_requestA | Универсальный отладочный вызов iiko API: любой метод и путь с автоматической v2-авторизацией. Возвращает HTTP-статус, correlationId и тело ответа. Пример: method=POST, path=/api/1/organizations, body={}. |
| iiko_access_tokenA | Получить (или принудительно обновить) access_token v2. Полезно для отладки авторизации: показывает выданный JWT. |
| iiko_organizationsA | Список организаций (POST /api/1/organizations). Возвращает organizationId для остальных вызовов. |
| iiko_nomenclatureC | Меню организации (POST /api/1/nomenclature). |
| iiko_stop_listsC | Стоп-листы по организациям (POST /api/1/stop_lists). |
| iiko_deliveries_by_idC | Статус доставок по orderIds (POST /api/1/deliveries/by_id). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools are mostly distinct resources, but the universal iiko_request overlaps with every specific wrapper, creating potential confusion about which to use. Although iiko_request is clearly for debugging, an agent might still misselect it for a routine operation.
All tool names follow a consistent snake_case convention with the iiko_ prefix, and they all use noun-like resource names. The naming pattern is uniform and predictable across the set.
Six tools is a well-scoped number for an API integration server, covering core resources with a generic fallback. It is within the ideal 3-15 range and each tool earns its place.
The specialized tools cover the primary endpoints (organizations, nomenclature, stop lists, deliveries), and the iiko_request tool provides a catch-all for any other API operation. This ensures no functional gaps or dead ends.