How to Connect Mirakl Connect to Cursor via MCP

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

Mirakl Connect + Cursor

Mirakl Connect for sellers: orders from every connected marketplace and sales channel in one place, returns, order documents, customer conversations and the Connect catalog with prices and stock. Not the single-marketplace Mirakl Seller API. Ship, cancel and accept are 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:

MIRAKL_CONNECT_CLIENT_ID, MIRAKL_CONNECT_CLIENT_SECRET

Step 1 — Get credentials

Not the Mirakl Seller API: the separate Mirakl Seller API connector (mirakl) talks to one Mirakl-powered marketplace at a time, through that marketplace's own https://<marketplace>.mirakl.net/api with a shop API key. Mirakl Connect is the seller-side channel platform above that: one login and one API (https://miraklconnect.com/api) for all the marketplaces and sales channels your company runs, with its own order ids, OAuth2 credentials and endpoints. Install this one when your company works in Mirakl Connect.

Setting up takes about 5 minutes.

1. Create OAuth2 API credentials for your company in Mirakl Connect, as described in Mirakl's guide Integrating with Connect APIs (Mirakl Connect help for sellers). You get a client ID and a client secret; the secret is shown once.
2. Paste them into MIRAKL_CONNECT_CLIENT_ID and MIRAKL_CONNECT_CLIENT_SECRET. AnythingMCP exchanges them at the Mirakl Authentication System (https://auth.mirakl.net/oauth/token, client credentials grant) for a bearer token of about one hour and renews it by itself.
3. Install the connector and run mirakl_connect_list_orders: it lists your latest orders and confirms the credentials.

Order ids and channels: every order has a Connect order id (id), which mirakl_connect_get_order and the write tools take, and the channel's own order number in channel_order_id. The sales channel and store are in origin (channel_name, channel_store_name). The Mirakl Connect API has no endpoint that lists your connected channels; the AI reads them from the origin of the orders.

What it reads: orders from every connected channel, most recently updated first, with status, origin, order lines (product, quantity, price, taxes, line status), shipping and billing information and fulfillment type (FULFILLED_BY_SELLER or FULFILLED_BY_PARTNER); without updated_from or ids, Mirakl returns the last 30 days. The Connect product catalog with titles, brand, category, GTINs, images, standard and discount prices, stock quantities and attributes. Returns across channels, with status (REQUEST_INITIATED, REQUEST_DECLINED, OPENED, RECEIVED, CLOSED), return lines, method, RMA id, label URL, tracking and rejection reason. Order documents such as customer invoices, delivery slips and return labels. Customer conversations about orders, and the messages of one conversation with author, text and attachments. The outcome of an asynchronous order action.

Filters: orders filter by statuses, updated_from, fulfillment_type and order ids. Returns need updated_from. Documents need order ids or updated_from, and conversations need updated_from or conversation ids.

Switched off at install: mirakl_connect_ship_order (marks lines shipped and passes carrier and tracking to the channel, which usually notifies the customer), mirakl_connect_cancel_order_lines (the customer is refunded and notified on the channel; cannot be undone) and mirakl_connect_accept_order_lines (accepts or refuses lines in AWAITING_ACCEPTANCE; refusing cancels the line and cannot be undone). They act on the live sales channel, so an admin turns them on deliberately. Even then the AI shows you the order, the lines and the values and waits for your yes, taking the line ids from order_lines[].id of the order. These calls are asynchronous: they return an action_id, and the AI checks the outcome with mirakl_connect_get_action_status, because the channel can still reject the action.

Paging and limits: every list answers with next_page_token while more items exist, and the AI passes it as page_token. Orders and returns default to 10 per page (up to 100), documents and conversations to 50 (up to 100); products go up to 1000 per page, and the AI uses a small page size unless it needs the whole catalog. Mirakl asks to call the order, return and product lists at most once per minute when syncing. Dates are ISO 8601 with a time zone.

Common errors: 401 means the client ID or secret is wrong or the token expired. 403 means the API client lacks the scope for that call, for example connect:order:read or connect:shipment:create. 402 means the feature, for example conversations, is not part of the account's Mirakl Connect plan. 404 means an unknown order or conversation id. 429 means too many calls: wait for Retry-After.

The connector does not change prices or stock, does not reply to conversations, does not create returns and does not connect new channels. For one Mirakl marketplace without Mirakl Connect, use the Mirakl Seller API connector.

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 Cursor

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.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart Cursor.
3. Open Cursor → Settings → MCP and check that anythingmcp is listed and connected.
4. Start chatting: the agent can now call the Mirakl Connect tools.

Available tools

Example prompts

• "Which orders came in across all our channels since yesterday, grouped by channel?"
• "Find the order with channel order number 405-1234567-1234567 and show its lines and their status."
• "List the returns opened this week with their channel, reason and tracking."
• "Show the customer conversations updated today and summarise what each customer wants."
• "Ship order line 1 of this order with DHL tracking 00340434161234567890. Show me the order and the lines first."

FAQ

Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot