Connect Wildberries to Microsoft Copilot via MCP

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

Wildberries + Microsoft Copilot

Run a Wildberries seller account from an AI agent: FBS orders and their statuses, seller warehouses and stock levels, statistics on orders and sales, stock on WB warehouses, the sales report detail, product cards and prices, product feedbacks and buyer questions with answers, and buyer return claims. 34 tools across the WB API hosts, one API token.

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:

WILDBERRIES_API_TOKEN

Step 1 — Get credentials

One token covers every tool; each tool calls the right Wildberries API host by itself.

1. In the seller portal, open Settings → API integrations (Настройки → Доступ к API) and click Create token.
2. Choose the Base token type. Wildberries says Personal tokens must not be used in cloud services. A Base token has lower limits on several methods (see below).
3. Tick the categories you need: Marketplace (FBS orders, warehouses, stock), Statistics, Analytics (stock on WB warehouses), Finance (sales report), Content (product cards), Prices and Discounts, Feedbacks and Questions and Buyers Returns. Choose Read only unless the AI should update stock or prices, answer feedbacks and questions, or decide on returns.
4. Copy the token, which is shown once, into WILDBERRIES_API_TOKEN without Bearer. It is valid for 180 days; create a new one before it expires.
5. Call wildberries_ping to check the token, then wildberries_list_new_orders for the FBS orders waiting to be packed.

A 401 means the token is wrong or expired; a 403 means it lacks the category for that part of the API.

Feedbacks, questions and returns: the AI counts the feedbacks and buyer questions still waiting for an answer, lists them, drafts replies and publishes each one after you approve the text. Answers appear on the product page, and an answer can be changed once, within 60 days. Return claims of the last 14 days come with the decisions Wildberries allows for each one, and the AI sends the one you choose. A return decision cannot be undone. wildberries_reject_question is switched off at install.

Base token: 5 calls an hour for feedbacks and questions. With a Base token, all feedback and question calls together are limited to 5 an hour, one every 12 minutes, so only a few answers fit into an hour. Plan the batch with the AI: on a 429 it stops and picks up again after the wait time Wildberries gives. Return claims allow 1 call an hour with a Base token.

Other rate limits: Marketplace allows 300 requests a minute, and every 4xx answer counts as 10. Statistics on orders and sales: one call a minute, and only one every 3 hours with a Base token, so the AI calls them once with a start date and works from the result. Sales report detail: 2 a day with a Base token. Prices: 4 an hour with a Base token. On a 429, the wait time is in X-Ratelimit-Retry.

Stock on WB warehouses: wildberries_get_wb_warehouse_stocks answers 403 to a Base token. The report flow works instead: wildberries_create_stock_report, then wildberries_get_stock_report_status, then wildberries_download_stock_report.

Stock and prices: wildberries_update_stocks overwrites the stock amount (it does not add) and wildberries_set_prices changes live prices, so the AI confirms both with you. Read the stock back after an update: wrong field names still return 204 without changing anything.

Already installed? The feedback, question and return tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your token and any tools you added yourself stay as they are, and wildberries_reject_question arrives switched off, as on a new install. Tick Feedbacks and Questions and Buyers Returns on the token, or create a new one, if they were not ticked before.

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 Wildberries 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

• "How many feedbacks and buyer questions are waiting for an answer today?"
• "Draft friendly answers to the unanswered 4- and 5-star feedbacks and show them to me before publishing."
• "Show the open return claims and the decisions I can take on each one."
• "Which FBS orders are new right now, and how much stock of those sizes is left on my warehouse?"

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