Connect Mirakl to Microsoft Copilot via MCP

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

Mirakl + Microsoft Copilot

Run your shop on any Mirakl-powered marketplace (Leroy Merlin, Conforama, BUT, home24, Maisons du Monde, Vente-unique, ePrice, Decathlon, Carrefour and many more) from an AI agent: orders, acceptance, tracking and shipping, incidents, offers with prices and stock, offer and product imports, customer and operator messages, returns, order documents, invoices and transactions. One install per marketplace.

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_URL, MIRAKL_API_KEY

Step 1 — Get credentials

1. Sign in to the marketplace's seller back office (the Mirakl portal the operator gave you). Each operator runs its own Mirakl instance, so install the connector once per marketplace (for example Leroy Merlin and Conforama) and name each install after its marketplace.
2. Copy the portal's address without any path into MIRAKL_URL (the addresses of common marketplaces are listed below). Do not add /api: the connector adds it itself.
3. Click your user name in the top right corner, open My user settings and the API Key tab, generate a key (or copy the existing one) and paste it into MIRAKL_API_KEY, without Bearer. Generating a new key invalidates the old one, so any other tool still using it stops working.
4. Only if your user manages several shops on this marketplace (common on home24 and Vente-unique): set MIRAKL_SHOP_ID to the numeric id of the shop to use. Leave it empty for your default shop.
5. Install the connector and run mirakl_get_account. It shows the shop behind the key.

Marketplaces that run on Mirakl: the connector is the same on all of them; only the address and the key change.

• Leroy Merlin (ADEO): https://adeo-marketplace.mirakl.net
• Conforama: https://conforama-prod.mirakl.net
• BUT: https://but-prod.mirakl.net
• home24: https://home24.mirakl.net
• Maisons du Monde: https://maisonsdumonde-prod.mirakl.net
• Vente-unique: https://venteunique-prod.mirakl.net
• ePrice: https://marketplace.eprice.it

Other operators work the same way, including those on their own domain: use the address of the seller back office you sign in to.

Orders and incidents: the AI lists the orders waiting for acceptance, accepts or refuses each line, stores the carrier and tracking number and confirms the shipment. It also finds orders with an open incident and, once the customer's problem is solved, closes the incident on that order line with mirakl_resolve_incident. The documents attached to an order (delivery notes, shipping labels, customer invoices) are listed with name, type and upload date; the file itself opens in the back office.

Returns: the AI lists return requests with reason, RMA, tracking and the linked order. On marketplaces that use Mirakl returns and let the shop decide, it can accept or refuse a request and confirm that the goods arrived at your warehouse. Refunds stay in the back office.

Confirm first: accepting orders, tracking, shipping, closing incidents, return decisions, offer updates, messages and product imports act on the live marketplace. The AI shows you what will change (order lines, tracking number, old and new price or stock, message text) and waits for your yes. Refusing an order line cancels it for good, and a sent message cannot be taken back.

Prices and stock: mirakl_update_offers replaces the whole offer, and every field left out is reset (a missing quantity becomes 0), so the AI reads the offer first and sends it back complete with only your change. mirakl_import_offers is switched off at install, because its REPLACE mode deletes every offer missing from the file.

What it reads: orders with customer, address and incidents, your offers and other shops' offers on the same products, messages, returns, order documents, the operator's invoices and the transaction lines (sales, commissions, refunds, payouts), plus the marketplace's channels (country sites), carriers, shipping zones, shipping methods and logistic classes. With Enhanced Seller Invoicing the invoice list shows no new documents, so the AI reads the accounting document requests and the transactions instead.

Limits: Mirakl limits each API separately, and operators can tighten the limits. Product and offer imports run at most every 15 minutes, and comparing competitor offers allows about 5 calls a minute. A 429 answer says how many seconds to wait.

Common errors: 401: the key is wrong, was replaced by a newer one, or belongs to another marketplace. 403: your user lacks the right for this action. 404: the order, offer or thread does not exist for this shop, or MIRAKL_URL is not the seller back office address. 400: a wrong parameter, or an order in the wrong state.

The connector does not refund, cancel orders or move money, and each install works on one marketplace and one shop.

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 Microsoft Copilot

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.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Mirakl tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Which orders are waiting for acceptance right now, and which orders have an open incident?"
• "Compare our price for EAN 3700123456789 with the other shops' offers on this marketplace."
• "Set the stock of SKU LAMP-042 to 25, but show me the current offer and the new values before you change anything."
• "Draft a reply to the customer's message on order 20481937-A and show it to me before sending."
• "Which return requests on Leroy Merlin are waiting for our decision, and what reason did each customer give?"
• "The customer on order 20481937-A got a replacement. Close the incident on that order line, but show me the reason code first."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

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