How to Connect PlentyONE to Claude via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → PlentyONE, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

PlentyONE + Claude

PlentyONE (plentymarkets) e-commerce ERP: orders with items and addresses, order statuses and sales channels, items and variations with prices, barcodes and texts, stock per warehouse, categories, manufacturers, sales prices and contacts. Creating items and changing variations are included, installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

PLENTYONE_URL, PLENTYONE_USERNAME, PLENTYONE_PASSWORD

Step 1 — Get credentials

Setting up takes about 5 minutes. You need a PlentyONE system (formerly plentymarkets) on a plan above Lite, because Lite has no REST access, and a dedicated API user with its own role.

1. In PlentyONE open Setup → Account management → Roles, create a role for the AI, switch to Advanced and tick the REST API rights it needs, for example Items (show), Stock management (show), Categories (show), Orders and Order statuses (show) and CRM contacts (show). No REST right is active by default.
2. Under Setup → Account management → Accounts create a user with access Only API user, give it that role and a password.
3. Put the address of your system into PLENTYONE_URL, without /rest, for example https://p12345.my.plentysystems.com. PlentyONE shows it under Setup → Client → Settings, or use the address you sign in at.
4. Put the API user's username into PLENTYONE_USERNAME and its password into PLENTYONE_PASSWORD.
5. Install the connector and run plentyone_list_webstores: it lists the clients (webstores) of your system and shows that the sign-in works.

Sign-in renews itself: the connector signs in with the API user and keeps the access token, which is valid for 24 hours, then signs in again on its own. PlentyONE allows only a few signed-in sessions per user at the same time (3 by default, shared with the back end), so use a dedicated API user rather than a person's account.

What it reads: orders with addresses, order items, amounts, payments, documents and shipping packages; order statuses and sales channels (referrers such as webshop, Amazon, eBay or Otto); items and their variations, the sellable SKUs, with sales prices, barcodes, attribute values, images and suppliers; item names and descriptions per language; stock per warehouse; categories, manufacturers, units, sales price definitions and contacts (customers, suppliers, partners); and the clients (webstores) of the system.

Stock and orders: for each variation and warehouse the AI sees net stock (what can be sold), physical stock (what is on the shelf) and reserved stock (what open orders hold). It finds a variation by its number, part of the number, barcode (EAN), item name or category, and filters orders by status, sales channel and date. Long lists arrive page by page, so the AI keeps asking for the next page until it has them all.

Every right counts: the API user only sees the areas its role allows. If orders or contacts come back with 403, the answer names the missing right and you add it to the role.

Read-only as installed: with the default setup the connector only reads. Nothing in your orders, items, stock, prices or contacts changes.

Switched off at install: plentyone_create_item creates an item with one inactive variation, and plentyone_update_variation changes a variation's name, number, model, active flag, weight or dimensions. Both change the live catalogue that feeds your shop and marketplaces, so an administrator turns them on deliberately, and even then the AI shows you the change and waits for your yes.

Limits: on the Expand and Scale plans PlentyONE allows about 200 reads and 80 writes per user and minute, and answers 429 above that. The AI then waits a minute before trying again.

Common errors: 401 means a wrong username or password, or a user without API access. 403 lists the missing right in missing_permissions, for example order.show: add it to the user's role. A 404 on every call means PLENTYONE_URL is wrong.

The connector does not create, change or cancel orders, book stock, change prices or contacts, or delete anything.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Claude

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. PlentyONE, and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat: start typing prompts.

Available tools

Example prompts

• "Which Amazon orders from yesterday are still waiting for payment?"
• "How much of SKU 10045-BL can we still sell across all warehouses, and how much is held by open orders?"
• "Find the product with EAN 4012345678901 and show me its sales prices and stock."
• "Show me order 58213 with the delivery address and every item in it."
• "Look up the customer Smith Trading Ltd and show me their addresses and order summary."

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse