Summary
Run your shop on the Rue du Commerce marketplace from an AI agent: orders, acceptance, tracking and shipping, incidents, offers with prices and stock, imports, messages, returns, invoices and transactions. The marketplace sells in France; sign in with the shop API key from your Rue du Commerce seller back office.
Guided setup
Connect Rue du Commerce Marketplace to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Rue du Commerce Marketplace in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Rue du Commerce Marketplace
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Rue du Commerce Marketplace, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Rue du Commerce Marketplace + Microsoft Copilot
Run your shop on the Rue du Commerce marketplace from an AI agent: orders, acceptance, tracking and shipping, incidents, offers with prices and stock, imports, messages, returns, invoices and transactions. The marketplace sells in France; sign in with the shop API key from your Rue du Commerce seller back office.
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:
RUE_DU_COMMERCE_API_KEY
Step 1 — Get credentials
Countries: France.
Who can sell: Rue du Commerce selects its sellers; contact it by e-mail ([email protected]) or through its seller form. The connector needs a seller account that Rue du Commerce has already opened.
Setting up takes about 5 minutes.
- Sign in to the Rue du Commerce seller back office:
https://mirakl-web.groupe-rueducommerce.fr/login. - In the back office open your e-mail address (top right) > My account > API key and click Generate a new key (or copy the existing key). Paste it into
RUE_DU_COMMERCE_API_KEY. The key is sent as is in theAuthorizationheader, withoutBearer. Generating a new key invalidates the old one, so any other tool using it stops working. - Leave
RUE_DU_COMMERCE_SHOP_IDempty. Only if your user manages several shops on Rue du Commerce, setRUE_DU_COMMERCE_SHOP_IDto the numeric id of the shop this connector should work on (shown on the dashboard of the back office next to Identifier or Shop ID, and returned asshop_idbyrue_du_commerce_get_account). Without it your default shop is used. - Install and run
rue_du_commerce_get_account: it returns the shop the key belongs to.
Where to start: rue_du_commerce_get_account shows the shop behind the key (id, name, state, currency and channels). For the daily work use rue_du_commerce_list_orders with order_state_codes=WAITING_ACCEPTANCE, rue_du_commerce_list_offers for prices and stock and rue_du_commerce_list_threads for messages that wait for a reply.
Products and competing offers: rue_du_commerce_get_products looks products up in the Rue du Commerce catalog by EAN or another reference and returns the marketplace product SKU; rue_du_commerce_list_product_offers lists the offers of every shop for given products, best price first, at about 5 calls a minute.
Order workflow: a new order waits in WAITING_ACCEPTANCE. rue_du_commerce_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then rue_du_commerce_update_tracking stores the carrier and tracking number (carrier codes come from rue_du_commerce_list_carriers) and rue_du_commerce_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use rue_du_commerce_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; rue_du_commerce_resolve_incident closes an incident on one order line once it is solved. Documents attached to orders (delivery notes, labels, customer invoices) are listed by rue_du_commerce_list_order_documents.
Writes: confirm first. rue_du_commerce_accept_order, rue_du_commerce_update_tracking, rue_du_commerce_ship_order, rue_du_commerce_resolve_incident, rue_du_commerce_accept_return, rue_du_commerce_receive_return, rue_du_commerce_update_offers, rue_du_commerce_reply_thread, rue_du_commerce_create_order_thread and rue_du_commerce_import_products act on the live marketplace. Before each call, show the user what will change (order id and lines, tracking number, offer SKU with the old and new price or stock, the message text and recipients) and wait for a yes. Refusing an order line cancels it for good. No tool here refunds, cancels orders or moves money; do that in the back office. rue_du_commerce_import_offers can delete offers (REPLACE mode deletes every offer missing from the file), so it is installed switched off.
Updating offers (prices and stock): rue_du_commerce_update_offers (OF24) replaces the whole offer. Every field you leave out is reset: a missing quantity becomes 0, a missing discount or description is deleted. Always read the offer first (rue_du_commerce_get_offer or rue_du_commerce_list_offers with sku) and send it back complete with only the intended change: shop_sku, product_id and product_id_type (from product_references), state_code, price, quantity, leadtime_to_ship, logistic_class (its code), min_quantity_alert, description, discount, all_prices, available_started / available_ended (read as available_start_date / available_end_date) and any offer_additional_fields. Leave update_delete empty or update. The call returns an import_id; the change is applied asynchronously, so check it with rue_du_commerce_get_offer_import before reading the offer again. Condition codes for state_code come from rue_du_commerce_list_offer_conditions, logistic class codes from rue_du_commerce_list_logistic_classes.
File imports: rue_du_commerce_import_products (P41) and rue_du_commerce_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format Rue du Commerce asks for; the connector downloads it and uploads it to Rue du Commerce. Track them with rue_du_commerce_list_product_imports / rue_du_commerce_get_product_import and rue_du_commerce_list_offer_imports / rue_du_commerce_get_offer_import.
Returns: rue_du_commerce_list_returns (RT11) lists return requests. Where Rue du Commerce lets the shop decide, rue_du_commerce_accept_return accepts or refuses one in WAITING_ACCEPTANCE and rue_du_commerce_receive_return confirms the goods arrived. Refunds stay in the back office.
Messages: rue_du_commerce_list_threads lists conversations (filter with entity_type=MMP_ORDER and entity_id=<order id> for one order; entity_id without entity_type is refused), rue_du_commerce_get_thread reads one with its messages, rue_du_commerce_reply_thread answers (recipient CUSTOMER or OPERATOR, which is Rue du Commerce) and rue_du_commerce_create_order_thread opens a new conversation on an order. Reason codes for topics come from rue_du_commerce_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).
Money: rue_du_commerce_list_invoices (IV01) lists the accounting documents Rue du Commerce issues to the shop and rue_du_commerce_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If Rue du Commerce uses Enhanced Seller Invoicing, IV01 returns no new documents; use rue_du_commerce_list_document_requests (DR11) and the transactions then.
Reference lists: rue_du_commerce_list_channels (country sites), rue_du_commerce_list_carriers, rue_du_commerce_list_shipping_zones, rue_du_commerce_list_shipping_methods and rue_du_commerce_list_logistic_classes change rarely; read them once per conversation.
Pagination: orders, offers, invoices and product imports page with max (at most 100) and offset. Threads, returns, transactions, document requests and offer imports return a next_page_token; pass it as page_token to get the next page (all other filters are then ignored) until it is missing.
Dates are ISO 8601, e.g. 2026-10-01T00:00:00Z; answers are in UTC.
Rate limits: Each API has its own limit and Rue du Commerce can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, rue_du_commerce_get_account and the reference lists about once a day. A 429 carries a Retry-After header with the seconds to wait; do not retry in a loop.
Errors: 401 means the key is wrong or was replaced by a newer one, 403 that your user lacks the right for this action, 404 that the order, offer or thread does not exist for this shop, 400 a wrong parameter or an order in the wrong state (the message names it, e.g. ORDER_INVALID_STATE).
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 showsYOUR_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.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - 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.
- Try it in the agent's Test pane: ask for something that needs the
Rue du Commerce Marketplacetools. - 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
| Tool | What it does |
|---|---|
rue_du_commerce_get_account | Read the shop behind the API key on this marketplace (A01): shop id and name, state, channels, currency, grade and approval rate, contact… |
rue_du_commerce_list_orders | List orders (OR11) with their lines, customer, shipping address, prices, state and incidents. Filter by state (e.g. WAITING_ACCEPTANCE for… |
rue_du_commerce_list_offers | List the shop's offers (OF21): SKU, product, price and discount, all channel prices, quantity in stock, condition, lead time and whether… |
rue_du_commerce_get_offer | Read one offer in full by its offer id (OF22): every price field, discount, quantity, condition, logistic class, lead time and custom… |
rue_du_commerce_list_offer_conditions | List the offer conditions (OF61) the marketplace accepts, e.g. new or used, with the code to put in state_code when updating offers |
rue_du_commerce_list_offer_imports | List offer imports and updates (OF04), from files and from rue_du_commerce_update_offers: status (WAITING, RUNNING, COMPLETE, FAILED)… |
rue_du_commerce_get_offer_import | Read the status of one offer import or offer update (OF02) by its import_id, as returned by rue_du_commerce_update_offers or… |
rue_du_commerce_export_offers | Start an export of all the shop's offers as files (OF52), the way to read the whole catalogue (every SKU with price and stock) instead of paging rue_du_commerce_list_offers |
rue_du_commerce_get_offer_export_status | Status of an offer export started with rue_du_commerce_export_offers (OF53): PENDING, COMPLETED or FAILED, and once COMPLETED the urls of the files |
rue_du_commerce_get_offer_export_file | Read one file of a completed offer export (OF54): the offers with their SKU, product, quantity, prices and the other exported fields, as JSON or CSV |
rue_du_commerce_list_product_imports | List product imports (P51) with their status (WAITING, RUNNING, SENT, COMPLETE, FAILED, CANCELLED), the transformation counts and the… |
rue_du_commerce_get_product_import | Read the status of one product import (P42) by its import_id: import status, reason, transformation counts and the integration details… |
rue_du_commerce_get_products | Look up products in the marketplace catalog by their identifiers (P31), e.g. EAN, and get the marketplace product SKU, title and category.… |
rue_du_commerce_list_product_offers | List the offers of every shop for given products (P11), sorted by best price, to compare your price with the competition. Give product_ids… |
rue_du_commerce_list_threads | List message threads (M11) with customers and Rue du Commerce: topic, linked order or offer, participants, last message date and since when… |
rue_du_commerce_get_thread | Read one message thread (M10) with all its messages, senders, recipients, attachments and the linked order or offer |
rue_du_commerce_list_returns | List return requests (RT11) with their state, return lines, reason, RMA, tracking and the linked order. Filter by state, order or date.… |
rue_du_commerce_list_reasons | List the marketplace's reason codes (RE01): incident, cancellation, refund and message reasons, with their labels and whether the shop may… |
rue_du_commerce_list_carriers | List the carriers the marketplace knows (SH21) with their code, label and tracking URL. Use the code as carrier_code in… |
rue_du_commerce_list_invoices | List the accounting documents Rue du Commerce issues to the shop (IV01): invoices and credit notes with period, totals with and without… |
rue_du_commerce_list_transactions | List the shop's transaction lines (TL02): order amounts, shipping, commissions, refunds, manual credits and payouts, with amount, type… |
rue_du_commerce_list_document_requests | List accounting document requests (DR11), used when Rue du Commerce runs Enhanced Seller Invoicing: invoices and credit notes that Rue du… |
rue_du_commerce_list_order_documents | List the documents attached to one or more orders (OR72): delivery notes, shipping labels, customer invoices and other files, with id, file… |
rue_du_commerce_list_channels | List the marketplace's sales channels (CH11), usually one per country site, with code and label. Use the codes as channel_codes in… |
rue_du_commerce_list_shipping_zones | List the active shipping zones of the marketplace (SH11) with code and label, e.g. mainland France or Corsica. Changes rarely: call it… |
rue_du_commerce_list_shipping_methods | List the active shipping methods of the marketplace (SH12), e.g. standard, express or pick-up, with code, label, whether a tracking number… |
rue_du_commerce_list_logistic_classes | List the marketplace's logistic classes (SH31), the size or weight bands that decide shipping prices, with code and label. Use the code as… |
rue_du_commerce_accept_order | Accept or refuse the lines of an order waiting for acceptance (OR21). Every line of the order must be listed. Refusing a line cancels it… |
rue_du_commerce_update_tracking | Set the carrier and tracking number of an order (OR23). Give carrier_code from rue_du_commerce_list_carriers, or carrier_name with… |
rue_du_commerce_ship_order | Confirm that an order in SHIPPING has been shipped (OR24); it moves to SHIPPED and the customer is notified. Set the tracking first with… |
rue_du_commerce_update_offers | Create or update offers, including price and stock (OF24). Replaces each offer completely: every field left out is reset (a missing… |
rue_du_commerce_reply_thread | Reply in a message thread (M12) to the customer or Rue du Commerce. The message is delivered at once and cannot be taken back: show the… |
rue_du_commerce_create_order_thread | Start a new message thread on an order (OR43) with the customer, Rue du Commerce or both. The message is delivered at once: show the user… |
rue_du_commerce_resolve_incident | Mark the open incident on one order line as resolved (OR64), once the customer's problem is solved. reason_code must be an INCIDENT_CLOSE… |
rue_du_commerce_accept_return | Accept or refuse a return request in WAITING_ACCEPTANCE (RT21). Only when Rue du Commerce handles returns in the seller back office and… |
rue_du_commerce_receive_return | Confirm that the goods of an accepted return arrived at your warehouse (RT25). The return moves to RECEIVED. Acts on the live marketplace… |
rue_du_commerce_import_products | Send a product file to the marketplace (P41) to create or enrich products in its catalog. file_url is the address of a CSV, XLSX or XML… |
rue_du_commerce_import_offers | Import an offer file (OF01) to create, update or delete offers in bulk. REPLACE mode deletes every offer that is not in the file, and… |
Example prompts
- "Which Rue du Commerce orders are waiting for my acceptance?"
- "Who has the best price for the SSD with EAN 8806094215038 on Rue du Commerce, and where does mine rank?"
- "Set the stock of my gaming mouse SKU GM-RGB-16K to 40."
- "Show the invoices Rue du Commerce issued me in October."
- "Add Chronopost tracking XY123456789FR to order 7712004-A and mark it shipped."
FAQ
Where do I get the Rue du Commerce API key? In the Rue du Commerce seller back office: your e-mail address (top right), My account, API key, then Generate a new key (or copy the existing key). Generating a new key invalidates the old one. If your user has more than one shop, set RUE_DU_COMMERCE_SHOP_ID; otherwise your default shop is used.
Who can sell on Rue du Commerce, and which countries does it cover? Rue du Commerce selects its sellers; contact it by e-mail ([email protected]) or through its seller form. The connector covers France.
Can it cancel orders, refund or delete offers? No tool refunds or cancels an order; do that in the Rue du Commerce back office. Refusing a line when accepting an order cancels it for good, so the AI shows you every write and waits for a yes. rue_du_commerce_import_offers installs switched off, because its REPLACE mode deletes every offer that is missing from the file; switch it on on the connector page only if the AI should use it.
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
Was this guide helpful?