Review PlentyONE orders, items, stock and contacts; add comments and update order status. For ecommerce teams managing orders and inventory in PlentyONE. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"plentymarkets": {
"url": "https://plentymarkets.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"plentymarkets": {
"type": "http",
"url": "https://plentymarkets.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Find recent unpaid orders, inspect their details and translate status IDs into the statuses used by your team.
plentymarkets_list_orders plentymarkets_get_order plentymarkets_list_order_statuses
Review physical, reserved and net stock by variation and warehouse, then inspect the related product variations.
plentymarkets_list_stock plentymarkets_list_warehouses plentymarkets_list_variations
Find a contact by email, inspect their account details and review their orders before responding to a customer query.
plentymarkets_list_contacts plentymarkets_get_contact plentymarkets_list_orders
Review existing comments and add an internal note to the selected order, keeping it hidden from the customer unless you explicitly request visibility.
Changes data · plentymarkets_list_comments plentymarkets_add_comment
Inspect an order and available statuses, confirm the target status, then apply it. A status change can trigger configured customer emails, stock bookings and other event procedures.
Changes data · plentymarkets_get_order plentymarkets_list_order_statuses plentymarkets_update_order_status
The login page asks for your Plenty ID, Back end user name and Back end user password.
The plenty ID is the number in your system's address: p12345.my.plentysystems.com. Create a dedicated back end user for this under Setup » Settings » User » Accounts and give it only the REST API and the user rights you want the assistant to have (orders, items, stock, contacts); every right the user has, the assistant has. The REST API needs the Expand contract or higher. Your login is stored encrypted and used only to call your system on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Plenty ID, Back end user name and Back end user password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the PlentyONE connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
plentymarkets_list_orders | read | 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 items unless add_order_items is false. GET /rest/orders. |
plentymarkets_get_order | read | Get an 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 | read | Get an order's 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | Get an item Get one item by id: flags, manufacturer, texts, condition, age rating and the item-level settings. GET /rest/items/{itemId}. |
plentymarkets_list_variations | read | 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 ...). GET /rest/items/variations. |
plentymarkets_list_categories | read | List categories List item categories (the category tree: id, parent, level, type, names with `with` details). GET /rest/categories. |
plentymarkets_list_manufacturers | read | List manufacturers List the manufacturers (brands) of the items: id, name, address data. GET /rest/items/manufacturers. |
plentymarkets_list_sales_prices | read | List sales price configurations 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 | read | 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 | read | List warehouses List the warehouses (id, name, type, priority, address settings). GET /rest/stockmanagement/warehouses. |
plentymarkets_list_contacts | read | 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 | read | Get a 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 a 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 | Change an order's 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. PUT /rest/orders/{orderId}. |
plentymarkets_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
plentymarkets_request_feature | Request a missing feature Tell usefulapi that the user needs something the PlentyONE tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
plentymarkets_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on PlentyONE (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
plentymarkets_cancel_subscription | Cancel the Pro subscription Cancel the caller's PlentyONE Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run plentymarkets_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper system and API user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this PlentyONE server only. Subscribe with plentymarkets_upgrade (it returns a Stripe Checkout link). Cancel any time with plentymarkets_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running plentymarkets_upgrade before then undoes the cancel. Or write to [email protected].
Review unpaid orders. Find stock that needs attention. Review a customer’s orders. Add an internal order note. Change an order’s status. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by PlentyONE. The server calls the PlentyONE API with your own PlentyONE access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Plenty ID, Back end user name and Back end user password. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Plenty ID, Back end user name and Back end user password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the PlentyONE API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in PlentyONE.
Yes, if you approve it. 2 of the 18 PlentyONE tools can create or change data. The other 16 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this PlentyONE server only. Cancel any time: Pro then runs to the end of the paid period. Run plentymarkets_usage_status to see how many calls you used.
Ask the AI to run plentymarkets_upgrade: it returns a Stripe Checkout link. To cancel, run plentymarkets_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with plentymarkets_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.