M.Video MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MVIDEO_API_KEY | Yes | Seller API key for M.Video / Eldorado OmniNet. | |
| MVIDEO_API_BASE | No | Base URL for the M.Video API. | https://omni-net.sellers.mvideo.ru |
| MVIDEO_DEFAULT_LOCATION_ID | No | Default location ID for stock tools. |
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 |
|---|---|
| mvideo_healthA | Return sanitized MCP/API configuration. Does not call M.Video and never returns the API key. |
| mvideo_merchant_location_listC | List seller warehouses and their marketplace connections. |
| mvideo_product_mapping_listC | Read offer_id to product_id mappings. |
| mvideo_stock_infoB | Read stock counts by product_id, offer_id, and/or location_id. |
| mvideo_price_infoA | Read prices by product_id and/or offer_id. Monetary values are returned in kopecks. |
| mvideo_price_updateA | Update RUB prices. Pass price/old_price/min_price in kopecks. Use dry_run=true to inspect the request before sending. |
| mvideo_stock_updateA | Update product stock counts. Use dry_run=true to inspect the request before sending. |
| mvideo_order_fbs_listB | Read FBS orders. Pass OmniNet filter fields as a raw JSON object when needed. |
| mvideo_order_fbs_status_listC | Read FBS order status updates. Pass OmniNet filter fields as a raw JSON object when needed. |
| mvideo_order_fbs_labels_getA | Get FBS order labels. Pass the exact OmniNet request object from the order workflow. |
| mvideo_order_fbs_exemplar_setA | Set required FBS exemplar/marking data. Defaults to dry-run; live write requires confirm. |
| mvideo_shipment_createA | Create a shipment for FBS orders. Defaults to dry-run; live write requires idempotency_key and confirm. |
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 targets a distinct resource-action pair (stock, price, orders, shipments, mappings). Even the two order-read tools are clearly separated by 'orders' vs 'status updates'. No ambiguity in purpose across the set.
All tools use a consistent `mvideo_` prefix and snake_case. Most follow a resource_action pattern (e.g., stock_update, order_fbs_list), but `mvideo_health` breaks the pattern and action verbs vary between list/info/get/set. Still predictable overall.
12 tools is well-scoped for a marketplace integration covering core areas: locations, product mappings, stock, prices, orders, and shipments. Each tool has a clear purpose and the count feels neither sparse nor bloated.
The surface covers read/write for stock and price, read for mappings and locations, and a full FBS order workflow (list, status, labels, exemplar, shipment). Minor gaps exist (e.g., no product mapping update or order cancellation), but core operations are present.