Skip to main content
Glama
damurka

jumia-vendor-center

by damurka

Related Servers

Alternatives to jumia-vendor-center

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing SumUp accounts (catalog, stock, sales, payouts) via natural language in MCP clients, accessing both the public API and undocumented dashboard endpoints.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Amazon Selling Partner API tools for sellers to manage orders, inventory, listings, pricing, analytics, and reports via natural language.
      4 npm
      1
      AGPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      84
      9 npm
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 27 tools

    Disambiguation4/5

    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).

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues