PlentyONE MCP by usefulapi

io.usefulapi/plentymarkets · v1.0.1 · ecommerce

PlentyONE MCP by usefulapi is healthy: it completed an MCP handshake in 590 ms and exposes 18 tools.

Review PlentyONE orders, items, stock and contacts; add comments and update order status.

Endpoint: https://plentymarkets.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count18
Latency590 ms
Last checked (UTC)2026-10-30T13:15:21.517Z

Health history

Checked (UTC)StatusLatencyError
2026-10-30T13:15:21.517ZHealthy590

Tools (18)

plentymarkets_list_ordersList orders (sales orders, returns, credit notes ...) with filters. Newest first with sort_by createdAt and sort_order desc. Returns {page, totalsCount, isLastPage, entries[]}; each entry has the id, typeId (1 = sales order), statusId, plentyId, createdAt, amounts and the order items unless add_orde
plentymarkets_get_orderGet one order by id: status, amounts, dates, properties, order items, address relations. Add related data with `with` (addresses, comments, payments, documents, shippingPackages ...). GET /rest/orders/{orderId}.
plentymarkets_get_order_status_historyThe status changes of an order: which status, when, and by which user. GET /rest/orders/{orderId}/status-history.
plentymarkets_list_order_statusesThe order statuses defined in the system (id and name per language), to translate a statusId. Optionally a range of status ids. GET /rest/orders/statuses.
plentymarkets_list_order_referrersThe order referrers (sales channels: shop, eBay, Amazon, ...) with their ids, for the referrer_id filter of plentymarkets_list_orders. GET /rest/orders/referrers.
plentymarkets_list_commentsThe comments (internal notes) on an order, an order item, a contact or a category. GET /rest/comments/{referenceType}/{referenceValue}.
plentymarkets_list_itemsList items (the product containers) with filters. Prices, stock, barcodes and SKUs belong to the variations: use plentymarkets_list_variations for those. Returns {page, totalsCount, isLastPage, entries[]}. GET /rest/items.
plentymarkets_get_itemGet one item by id: flags, manufacturer, texts, condition, age rating and the item-level settings. GET /rest/items/{itemId}.
plentymarkets_list_variationsSearch variations (the sellable products: number, SKU, barcodes, prices, stock, categories). Filter by item, number, barcode, SKU, active flag, category, warehouse. Use `with` for the related data (variationSalesPrices, variationBarcodes, stock, variationCategories, images ...). GET /rest/items/vari
plentymarkets_list_categoriesList item categories (the category tree: id, parent, level, type, names with `with` details). GET /rest/categories.
plentymarkets_list_manufacturersList the manufacturers (brands) of the items: id, name, address data. GET /rest/items/manufacturers.
plentymarkets_list_sales_pricesList the sales price configurations (price types such as retail or purchase price: id, type, names, which stores, countries and currencies they apply to). The prices of a variation: plentymarkets_list_variations with variationSalesPrices. GET /rest/items/sales_prices.
plentymarkets_list_stockList physical stock per variation and warehouse (physical stock, net stock, reserved, reorder level), optionally for one variation or changed since a date. Returns {page, totalsCount, isLastPage, entries[]}. GET /rest/stockmanagement/stock.
plentymarkets_list_warehousesList the warehouses (id, name, type, priority, address settings). GET /rest/stockmanagement/warehouses.
plentymarkets_list_contactsList contacts (customers, suppliers, ...). Returns personal data of your customers (names, emails, addresses). Filter by email, name, number, type, postal code or town; `with` adds addresses, options (email, phone), accounts, orderSummary. GET /rest/accounts/contacts.
plentymarkets_get_contactGet one contact by id (customer personal data). Add addresses or accounts with `with` (the relations documented for this single-contact route). GET /rest/accounts/contacts/{contactId}.
plentymarkets_add_commentWRITE: add an internal comment to an order, order item, contact, category or variation (an additive note, nothing is overwritten). By default the comment is NOT visible to the customer; only make it visible when the user explicitly asks. POST /rest/comments.
plentymarkets_update_order_statusWRITE: move an order to another status. This can trigger the event procedures configured in the system (customer emails, stock bookings, documents, shipping), so confirm the target status with the user first (plentymarkets_list_order_statuses has the ids). Only the status is sent. PUT /rest/orders/{