horoshop-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOROSHOP_LOGIN | No | API login created in the Horoshop admin panel | |
| HOROSHOP_TOKEN | No | Optional token if you already use token-based access | |
| HOROSHOP_BASE_URL | Yes | Your Horoshop store domain, e.g., https://your-store.example.com | |
| HOROSHOP_PASSWORD | No | API password created in the Horoshop admin panel |
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 |
|---|---|
| horoshop_authC | Authenticates with Horoshop and returns token metadata. |
| horoshop_list_ordersC | Returns orders using the Horoshop orders/export endpoint. |
| horoshop_get_orderB | Returns a single order by id using the Horoshop API. |
| horoshop_list_productsC | Returns products using the Horoshop catalog/export endpoint. |
| horoshop_get_productB | Returns a product by id using the Horoshop API. |
| horoshop_update_order_statusC | Updates an order status using the Horoshop API. |
| horoshop_call_apiC | Calls any Horoshop API function with arbitrary JSON parameters. |
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 7 tools
Most tools are clearly distinct (list vs get, orders vs products), and auth is separate. However, horoshop_call_api is a catch-all that could overlap with any tool, introducing some ambiguity about when to use it versus the specific tools.
All tools follow the consistent pattern horoshop_ + verb + noun (e.g., list_orders, get_order, update_order_status). The only minor deviation is horoshop_auth, but it is still a recognizable action and fits the style.
With 7 tools, the count is well-scoped for a typical e-commerce API integration. Each tool covers a distinct core operation without unnecessary bloat or sparseness.
The core workflows for orders (list, get, update status) and products (list, get) are covered. Missing product creation/update and order creation are notable, but the horoshop_call_api fallback fills these gaps, making the surface reasonably complete.