CS-Cart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsC | Retrieve a list of products from the CS-Cart store |
| get_productC | Get detailed information about a specific product |
| create_productC | Create a new product in the CS-Cart store |
| update_productC | Update an existing product |
| delete_productC | Delete a product from the store |
| update_product_stockC | Update product stock quantity |
| get_categoriesB | Get list of product categories |
| get_ordersC | Retrieve orders from the CS-Cart store |
| get_orderC | Get detailed information about a specific order |
| update_order_statusD | Update order status |
| get_usersC | Get list of users/customers |
| get_sales_statisticsC | Get sales statistics for a specific period |
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 12 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as create/delete/get/update for products, get for orders/categories/users/statistics, and update for order status and product stock. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
Most tools follow a consistent verb_noun pattern (e.g., create_product, get_products, update_order_status), but there are minor deviations like 'get_categories' and 'get_users' which use plural nouns inconsistently compared to 'get_product' and 'get_order' (singular). Overall, naming is highly readable and predictable.
With 12 tools, this server is well-scoped for managing a CS-Cart store, covering key operations like product management, order handling, user and category retrieval, and sales statistics. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides strong coverage for core e-commerce workflows, including CRUD operations for products, order retrieval and status updates, and access to categories, users, and sales data. Minor gaps include no tools for creating or updating categories/users, but agents can work around this with the existing tools.