# PlentyONE MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## PlentyONE MCP

Review and manage PlentyONE orders, inventory, stock levels and customer contacts

- Record: https://musedirectory.ai/connector/plentyone-mcp
- Category: Shopping & Commerce
- Developer: usefulapi (https://usefulapi.io/plentymarkets/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1268ms, checked 2026-10-30T08:31:16Z
- Endpoint: https://plentymarkets.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-30T08:31:16Z)
- Source: Found in the official MCP Registry (io.usefulapi/plentymarkets) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fplentymarkets

Connects to PlentyONE e-commerce platform to view orders, items, variations, stock across warehouses, and customer contacts. Allows adding internal comments and updating order status to trigger workflows.

Example request: "Show me all orders from the past week that are still pending and let me update their status to shipped"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use PlentyONE MCP to help me. It is a free service with an MCP server at https://plentymarkets.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- plentymarkets_list_orders: List 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 i
- plentymarkets_get_order: Get 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_history: The status changes of an order: which status, when, and by which user. GET /rest/orders/{orderId}/status-history.
- plentymarkets_list_order_statuses: The 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_referrers: The 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_comments: The comments (internal notes) on an order, an order item, a contact or a category. GET /rest/comments/{referenceType}/{referenceValue}.
- plentymarkets_list_items: List 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_item: Get one item by id: flags, manufacturer, texts, condition, age rating and the item-level settings. GET /rest/items/{itemId}.
- plentymarkets_list_variations: Search 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 ...). 
- plentymarkets_list_categories: List item categories (the category tree: id, parent, level, type, names with `with` details). GET /rest/categories.
- plentymarkets_list_manufacturers: List the manufacturers (brands) of the items: id, name, address data. GET /rest/items/manufacturers.
- plentymarkets_list_sales_prices: List 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_stock: List 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_warehouses: List the warehouses (id, name, type, priority, address settings). GET /rest/stockmanagement/warehouses.
- plentymarkets_list_contacts: List 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_contact: Get 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_comment: WRITE: 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_status: WRITE: 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

Screening checks:
- MCP handshake: pass (Answered in 1268ms)
- Domain against threat feeds (Cloudflare security DNS): pass (plentymarkets.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (18 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)