kitcommerce-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KITCOMMERCE_API_KEY | Yes | Admin API key secret (sent as authorization) | |
| KITCOMMERCE_API_URL | Yes | Base URL of the API, e.g. https://api.litekart.in | |
| KITCOMMERCE_STORE_ID | Yes | Store id (sent as x-litekart-store) |
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 |
|---|---|
| list_productsA | List products with pagination, search and filters. |
| get_productA | Get a single product by id. |
| create_productA | Create a new product. Common fields: name, slug, price, mrp, sku, stock, active, description, categoryId, images (string[]). |
| update_productA | Update an existing product by id (partial update). |
| delete_productA | Delete a product by id. |
| bulk_update_product_statusA | Update the status/active state of many products at once. |
| list_categoriesC | List categories with pagination, search and filters. |
| get_categoryB | Get a single category by id. |
| create_categoryA | Create a new category. Common fields: name, slug, parentCategoryId (null for a top-level category), description, image, active. |
| update_categoryA | Update an existing category by id (partial update). |
| delete_categoryB | Delete a category by id. |
| list_collectionsA | List collections with pagination, search and filters. |
| get_collectionA | Get a single collection by id. |
| create_collectionB | Create a new collection. Common fields: name, slug, description, active, conditions. |
| update_collectionA | Update an existing collection by id (partial update). |
| delete_collectionB | Delete a collection by id. |
| list_couponsA | List coupons with pagination, search and filters. |
| get_couponB | Get a single coupon by id. |
| create_couponB | Create a new coupon. Common fields: code, type (percentage|fixed), amount, minPurchase, maxDiscount, startDate, endDate, usageLimit, active. |
| update_couponB | Update an existing coupon by id (partial update). |
| delete_couponB | Delete a coupon by id. |
| list_ordersC | List orders with pagination, search and filters. |
| get_orderA | Get a single order by id. |
| update_orderA | Update an existing order by id (partial update). |
| list_inventoryB | List inventory with pagination, search and filters. |
| get_inventoryA | Get a single inventory by id. |
| update_inventoryA | Update an existing inventory by id (partial update). |
| list_customersB | List store customers with pagination, search and filters. |
| get_customerA | Get a single customer/user by id. |
| get_dashboard_summaryA | Get the admin dashboard summary (sales, orders, revenue and other store stats). |
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 30 tools
Each tool is clearly scoped to a specific resource and action (e.g., product, order, coupon). There is no overlap between list/get/create/update/delete operations across different resource types, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_products, create_order, update_inventory). The one bulk operation (bulk_update_product_status) still fits the same convention.
30 tools is slightly on the high side, but each tool serves a meaningful purpose within the e-commerce admin domain. The breadth is justified by covering multiple resources (products, categories, collections, coupons, orders, inventory, customers, dashboard).
The tool surface provides full CRUD for most master data and appropriate partial operations for transactional data (orders, inventory, customers) where creation is not an admin responsibility. Minor gaps like missing order-level item management or customer updates are acceptable for the domain.