jumia-vendor-center
Related Servers
Alternatives to jumia-vendor-center
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables Lamoda sellers to manage their store via natural language through a MCP server that connects to the official Lamoda Seller API, supporting 155 methods for products, prices, orders, shipments, and more.MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing SumUp accounts (catalog, stock, sales, payouts) via natural language in MCP clients, accessing both the public API and undocumented dashboard endpoints.MIT
- AlicenseNot gradedqualityCmaintenanceExposes Amazon Selling Partner API tools for sellers to manage orders, inventory, listings, pricing, analytics, and reports via natural language.4 npm1AGPL 3.0
- AlicenseCqualityCmaintenanceEnables AI agents to run Amazon Vendor Central operations such as direct fulfillment, procurement, invoicing, and retail analytics through 40 MCP tools.40MIT
- AlicenseBqualityDmaintenanceEnables complete VTEX e-commerce platform integration through natural language, allowing management of catalog, inventory, pricing, promotions, orders, marketplace operations, checkout, customer data, and payment configurations via AI conversations.849 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-
TDQS
Scored across 27 tools
Most tools map cleanly to distinct resource+action pairs, with the update_products/update_price/update_stock boundaries explicitly carved out. The main overlap risk is pack_orders vs pack_orders_v2, though the versioned descriptions and get_shipment_providers guidance largely disambiguate them. The two find_* heuristic tools share a style but target clearly different outcomes (duplicates vs outdated).
The set follows a strong snake_case verb_noun convention throughout (list_*, get_*, create_*, update_*, find_*, deactivate_*). Minor deviations include the pack_orders_v2 version suffix and an inconsistent get_/list_ split between similar read operations (list_orders vs get_order_items). Overall the pattern is predictable enough for an agent to guess tool names.
At 27 tools the server is on the heavy side, but it spans multiple distinct sub-domains — product catalog, order fulfillment, consignments, and payouts — making the per-domain count reasonable. Each tool earns its place with a genuine distinct operation rather than redundant variants, aside from the pack_orders v1/v2 pair.
Product lifecycle coverage is strong: create, list, update mutable fields, update price/stock, deactivate, plus duplicate/outdated heuristics and a sync orchestration tool. Order fulfillment covers pack, label, ready-to-ship, and cancel, but there is no returns/refunds surface. Consignment support has create/update/stock-check but no way to list or fetch a single consignment, a workable minor gap.