kaspi-merchant-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KASPI_AUTH_TOKEN | Yes | Your Kaspi API token |
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_ordersA | List orders from Kaspi Marketplace. Filter by state, date range. Returns JSON:API response. |
| get_orderA | Get a single order by ID from Kaspi Marketplace. |
| get_order_itemsA | Get line items (entries) for an order. Returns products, quantities, prices. |
| accept_orderA | Accept a Kaspi order (set status to ACCEPTED_BY_MERCHANT). WARNING: This is IRREVERSIBLE! The order will be accepted and you must fulfill it. |
| complete_orderA | Mark a Kaspi order as COMPLETED. WARNING: This is IRREVERSIBLE! Only use when the order has been fully delivered. |
| cancel_orderA | Cancel a Kaspi order. WARNING: This is IRREVERSIBLE! The order will be cancelled and the buyer will be notified. |
| get_citiesA | Get the list of all Kaspi cities in Kazakhstan. |
| get_productsB | Get merchant product offers (merchantoffers) from Kaspi Marketplace. |
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 8 tools
Each tool has a distinct purpose: order lifecycle actions (accept, cancel, complete) and informational queries (get orders, products, cities). No overlap between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., accept_order, get_orders), making it easy to predict functionality.
With 8 tools, the set covers essential merchant operations without being overly large or sparse. It's well-scoped for Kaspi marketplace management.
Covers core order lifecycle (accept, cancel, complete) and retrieval, plus cities and products. Minor gap: no tool for updating products or marking orders as shipped, but it's acceptable.