Connect bol.com to Microsoft Copilot via MCP

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

bol.com + Microsoft Copilot

bol.com Retailer API for sellers on the Dutch and Belgian marketplace: orders, shipments with track and trace, returns, FBB inventory, offers with price and stock, commission, catalog content, competing offers, ratings, invoices and performance indicators. Client ID and secret.

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:

BOL_CLIENT_ID, BOL_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 3 minutes. You need a bol.com seller account (Verkopen via bol) and access to the API settings in the bol Seller Dashboard. The connector needs a client ID and a client secret for the Retailer API.

1. In the bol Seller Dashboard open your account, then Instellingen → Diensten → API Instellingen (Settings, Services, API settings). Save a technical contact if bol asks for one.
2. Under Client credentials voor de Retailer API click Aanmaken (Create), give the key a name and click Toon secret (Show secret).
3. Copy the client ID into BOL_CLIENT_ID and the secret into BOL_CLIENT_SECRET. If the secret is lost, create new credentials.
4. Install the connector. Run bol_com_list_orders to check the connection: it returns your open orders that you ship yourself (FBR).

Cloud and self-hosted work the same way: the credentials are the same, and there is no redirect URL or IP address to register.

Authentication: the connector exchanges the client ID and secret at https://login.bol.com/token (client credentials) for a bearer token that lasts about 5 minutes, and reuses it until it expires. It never asks for a new token on every call, because bol blocks addresses that hammer its login service.

Where to start: bol_com_list_orders lists open FBR orders, newest first; bol_com_get_order adds the customer's shipping and billing details and the items. bol_com_list_offers lists your offers and bol_com_list_inventory shows the stock that bol holds for you in its warehouses (FBB).

What it reads: orders, shipments with transport and track and trace, returns with reasons and customer comments, FBB stock, offers with price, stock and country availability, why an offer is not for sale, commission for a product at a price, bol catalog content by EAN, competing offers and who has the buy box, star ratings, visits and buy box percentage per offer, seller performance indicators per week, and invoices (read-only).

Shipping: bol_com_create_shipment confirms the shipment of items you ship yourself, with your carrier and track and trace code. bol_com_add_track_and_trace adds a missing code to a shipment; it cannot change an existing one.

Offers: bol_com_create_offer and bol_com_update_offer create offers and change price, stock, fulfilment, countries or the on-hold flag. An update only changes the fields given, but an array (bundle prices, countries) replaces the old one whole. A 409 means someone changed the offer at the same time. Prices are in EUR including VAT, and stock is 0 to 999.

Switched off at install: bol_com_cancel_order_item (cancel an order item you cannot deliver) and bol_com_delete_offer (delete an offer). A cancellation cannot be undone and counts against your seller score, and a deleted offer disappears from bol at once and cannot be restored. To pause an offer, set it on hold with bol_com_update_offer instead. Switch them on on the connector page only if the AI should use them; the AI asks you to confirm every change. Shipments, track and trace, and creating and updating offers are switched on.

Asynchronous writes: shipments, transports and cancellations answer with a process status instead of a result. bol_com_get_process_status (or bol_com_find_process_statuses by entity and event type) shows when it is SUCCESS or FAILURE. bol keeps process statuses for one day. Offers are synchronous.

Paging: order, shipment, return and inventory lists take page from 1 with 50 rows a page; an empty answer means there are no more pages. Offers use a cursor: pass page.nextCursor back until it is missing.

Rate limits: bol sets them per endpoint. The order list and the shipment list allow 25 calls a minute, returns and inventory 20 a minute, invoices 24 a minute; order details 25 a second and offers 25 to 50 a second. A 429 carries a Retry-After in seconds; the live values are at api.bol.com/retailer/public/ratelimits.

Ids and formats: order ids can contain letters (A4K8290LP0), EANs are strings, dates are YYYY-MM-DD and times ISO 8601 with an offset. Unused fields are left out, because bol answers 400 to empty strings.

Common errors: errors come as application/problem+json with title, detail and violations that name the field. 400 usually means a field is missing or empty. 429 is the rate limit: wait for the Retry-After time.

Not covered: handling or registering returns (accepting a return makes bol refund the customer), buying shipping labels and anything that moves money.

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 bol.com 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 open orders still need to ship today, and do any of them have a cancellation request?"
• "Show order A4K8290LP0 with the customer's address and the items."
• "Which of my offers are not for sale, and why?"
• "Who has the buy box on EAN 8712345678901, and at what price?"
• "Set the price of my offer for EAN 8712345678901 to 24.95 and the stock to 40."

FAQ

Can it handle returns or cancel orders? It reads returns but does not handle or register them, because accepting a return makes bol refund the customer. Cancelling an order item is possible with bol_com_cancel_order_item, which is switched off at install.

Does it work for Belgian and Dutch sales? Yes. One seller account covers both countries; offers carry their country availability, and bol_com_get_offer_not_for_sale_reasons explains per country why an offer is not for sale.

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