kaspi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KASPI_API_KEY | Yes | API-ключ из кабинета продавца Kaspi.kz |
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 |
|---|---|
| get_ordersB | Получение списка заказов Kaspi с фильтрацией по статусу и дате. |
| get_productsA | Получение списка товаров продавца на Kaspi. |
| get_orderA | Получение детальной информации о заказе Kaspi по 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 3 tools
get_orders and get_order are clearly list versus detail, and get_products targets a distinct resource. The singular/plural pair is the only possible source of confusion, but the descriptions resolve it.
All tools follow the consistent get_<resource> verb_noun pattern, with singular used for detail and plural for list operations. There is no style mixing or vague naming.
Three tools is well-scoped for a focused read-only Kaspi merchant integration. Each tool serves a distinct, necessary purpose with no redundancy.
The server covers order list, order detail, and product list, but lacks product detail and any write or state-change operations like order status updates. Real Kaspi seller workflows would hit significant dead ends.