vndly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VNDLY_API_KEY | Yes | Your VNDLY personal API key | |
| VNDLY_API_URL | No | Override for self-hosted VNDLY | https://www.vndly.io |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search VNDLY products and their variants (SKU, attributes, unit) by name, description, category, or SKU. Returns matching products with all variants. |
| list_ordersA | List recent purchase orders or sales orders from VNDLY, with supplier/customer names, totals, and status. Use type=purchase for supplier orders, type=sales for customer orders. |
| get_low_stock_alertsA | Return current low-stock reorder alerts from VNDLY. Each alert shows the product, SKU, suggested reorder quantity, and recommended supplier. |
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
Each tool targets a distinct resource and action: searching products, listing orders, and retrieving low stock alerts. There is no overlap or ambiguity in their purposes.
All tool names follow a consistent verb_noun pattern: search_products, list_orders, get_low_stock_alerts. The verbs (search, list, get) are varied but appropriately describe the actions, and the style is uniformly snake_case.
With 3 tools, the server is on the lean side but not unreasonably so. Each tool appears focused and purposeful, covering a specific read-oriented need for VNDLY data. It feels slightly thin but acceptable for a niche integration.
The tools only provide read operations (search, list, get alerts) with no create, update, or delete capabilities. Missing obvious operations like retrieving order details, viewing a specific product, or executing reorders create significant gaps for typical workflows.