Connect MediaMarkt to Microsoft Copilot via MCP

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

MediaMarkt Marketplace + Microsoft Copilot

Run your shop on the MediaMarkt 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 Germany, Austria, Spain, the Netherlands, Italy, Belgium, Switzerland, Poland and Hungary; sign in with the shop API key from your MediaMarkt 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:

MEDIAMARKT_API_KEY

Step 1 — Get credentials

Countries: Germany, Austria, Spain, the Netherlands, Italy, Belgium, Switzerland, Poland and Hungary. In Italy the marketplace trades as MediaWorld. All countries share one seller platform.

Who can sell: MediaMarkt takes applications through a form per country, followed by a business verification (KYC). The connector needs a seller account that MediaMarkt has already opened.

Setting up takes about 5 minutes.

1. Sign in to the MediaMarkt seller back office: https://mediamarktsaturn.mirakl.net/login.
2. In the back office open your login name (top right) > My user settings > API key and click Generate a new key (or copy the existing key). Paste it into MEDIAMARKT_API_KEY. The key is sent as is in the Authorization header, without Bearer. Generating a new key invalidates the old one, so any other tool using it stops working.
3. MediaMarkt usually opens one shop per country, so most sellers have several shops under one user. If your user has more than one shop, set MEDIAMARKT_SHOP_ID to 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 as shop_id by mediamarkt_get_account); to work on several shops, install the connector once per shop. Without it your default shop is used.
4. Install and run mediamarkt_get_account: it returns the shop the key belongs to.

Where to start: mediamarkt_get_account shows the shop behind the key (id, name, state, currency and channels). For the daily work use mediamarkt_list_orders with order_state_codes=WAITING_ACCEPTANCE, mediamarkt_list_offers for prices and stock and mediamarkt_list_threads for messages that wait for a reply.

Products and competing offers: mediamarkt_get_products looks products up in the MediaMarkt catalog by EAN or another reference and returns the marketplace product SKU; mediamarkt_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. mediamarkt_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then mediamarkt_update_tracking stores the carrier and tracking number (carrier codes come from mediamarkt_list_carriers) and mediamarkt_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use mediamarkt_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; mediamarkt_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 mediamarkt_list_order_documents.

Writes: confirm first. mediamarkt_accept_order, mediamarkt_update_tracking, mediamarkt_ship_order, mediamarkt_resolve_incident, mediamarkt_accept_return, mediamarkt_receive_return, mediamarkt_update_offers, mediamarkt_reply_thread, mediamarkt_create_order_thread and mediamarkt_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. mediamarkt_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): mediamarkt_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 (mediamarkt_get_offer or mediamarkt_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 mediamarkt_get_offer_import before reading the offer again. Condition codes for state_code come from mediamarkt_list_offer_conditions, logistic class codes from mediamarkt_list_logistic_classes.

File imports: mediamarkt_import_products (P41) and mediamarkt_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format MediaMarkt asks for; the connector downloads it and uploads it to MediaMarkt. Track them with mediamarkt_list_product_imports / mediamarkt_get_product_import and mediamarkt_list_offer_imports / mediamarkt_get_offer_import.

Returns: mediamarkt_list_returns (RT11) lists return requests. Where MediaMarkt lets the shop decide, mediamarkt_accept_return accepts or refuses one in WAITING_ACCEPTANCE and mediamarkt_receive_return confirms the goods arrived. Refunds stay in the back office.

Messages: mediamarkt_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), mediamarkt_get_thread reads one with its messages, mediamarkt_reply_thread answers (recipient CUSTOMER or OPERATOR, which is MediaMarkt) and mediamarkt_create_order_thread opens a new conversation on an order. Reason codes for topics come from mediamarkt_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).

Money: mediamarkt_list_invoices (IV01) lists the accounting documents MediaMarkt issues to the shop and mediamarkt_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If MediaMarkt uses Enhanced Seller Invoicing, IV01 returns no new documents; use mediamarkt_list_document_requests (DR11) and the transactions then.

Reference lists: mediamarkt_list_channels (country sites), mediamarkt_list_carriers, mediamarkt_list_shipping_zones, mediamarkt_list_shipping_methods and mediamarkt_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 MediaMarkt can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, mediamarkt_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 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 MediaMarkt Marketplace 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

• "List my MediaMarkt orders that are in SHIPPING and have no tracking number yet."
• "Who has the best price for the headphones with EAN 4548736132610 on MediaMarkt, and where does mine rank?"
• "Which of my MediaMarkt offers have fewer than 3 units left?"
• "Show the open incidents on my MediaMarkt orders and what the customers wrote."
• "Reply to the customer in the thread on order 4501234-A that the replacement ships tomorrow."

FAQ

Where do I get the MediaMarkt API key? In the MediaMarkt seller back office: your login name (top right), My user settings, API key, then Generate a new key (or copy the existing key). Generating a new key invalidates the old one. MediaMarkt usually opens one shop per country, so most sellers have several shops under one user. With more than one shop, set MEDIAMARKT_SHOP_ID to the shop this connector should work on.

Who can sell on MediaMarkt, and which countries does it cover? MediaMarkt takes applications through a form per country, followed by a business verification (KYC). The connector covers Germany, Austria, Spain, the Netherlands, Italy, Belgium, Switzerland, Poland and Hungary. In Italy the marketplace trades as MediaWorld. All countries share one seller platform.

Can it cancel orders, refund or delete offers? No tool refunds or cancels an order; do that in the MediaMarkt 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. mediamarkt_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

• Connector landing page
• Connect to Claude