How to Connect QLS to Microsoft Copilot via MCP

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

QLS + Microsoft Copilot

Pakketdienst QLS (Netherlands): parcel shipments with labels and tracking, shipping products and service points, fulfilment orders picked from the QLS warehouse, fulfilment products and stock, backorders, returns and inbound purchase orders. Deleting products and cancelling orders install switched off.

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:

QLS_USERNAME, QLS_PASSWORD

Step 1 — Get credentials

Setting up takes about 5 minutes. You need an account on mijn.pakketdienstqls.nl.

1. QLS authenticates the API with HTTP Basic and the login details of the mijn.pakketdienstqls.nl portal. Where your account allows it, use a separate user for the API (ask QLS IT support at [email protected]), so that a person changing their password does not break the connector.
2. Put the user name (usually an email address) in QLS_USERNAME and the password in QLS_PASSWORD.
3. Install the connector and run qls_list_companies. It returns the company id (a UUID) that every other tool takes as company_id; qls_get_company shows one company.

Which API: the QLS Fulfilment and Parcel Service API on https://api.pakketdienstqls.nl (OpenAPI at https://api.pakketdienstqls.nl/swagger/). QLS publishes a v1 and a v2; the connector uses v2 where QLS offers it (shipment creation, returns, purchase orders) and v1 for the rest.

Ids you need first: the company id from qls_list_companies; the brand id from qls_list_brands (a brand carries the sender, return and customs addresses and is needed for shipments and orders); the shipping products from qls_list_shipping_products, with combinations[].id as the product_combination_id, options[].tag as delivery options, prices per country and weight band and maximum dimensions. Pick-up points come from qls_list_service_points or, for one shipping product, qls_list_product_service_points; their servicepoint_code goes on the shipment or order.

What it reads: parcel shipments with status (created, printed, pre_transit, in_transit, delivered, returned_to_sender), barcode, tracking id and tracking URL, filtered by reference, barcode, status, brand, receiver fields, dates or free search; one shipment with its weight and, with with_label, the PDF and ZPL label URLs; the return shipment of a parcel; fulfilment orders with status, ordered, reserved and delivered amounts, receiver, deliveries and the shipments that left the warehouse; fulfilment products with EAN, SKU, article number, prices, stock totals and warehouse locations (zone, rack, shelf, best-before); stock per product (total, reserved, available, salable, sold, backorder, incoming, forecast) and per warehouse location with batch; backorders; returns with status, consumer, original shipment and order and the returned products with reason; purchase orders (announced inbound deliveries) with status, products, suppliers and deliveries, including those in transit; suppliers.

What it writes: qls_create_shipment books a parcel with the carrier and returns barcode, tracking URL and label_pdf_url; sender and return address default to the brand. qls_create_fulfillment_order lets QLS pick, pack and ship products from your stock. qls_update_fulfillment_order puts an order on hold, releases it or changes the processable date, reference, remarks or service point. qls_create_fulfillment_product and qls_update_fulfillment_product maintain articles; qls_create_return_from_order announces a return; qls_create_purchase_order announces goods coming to the warehouse. A shipment costs money and a fulfilment order ships real stock, so before every write the AI shows receiver, products and amounts and shipping product and waits for your yes.

Switched off at install: qls_delete_fulfillment_product and qls_cancel_fulfillment_order, which cannot be undone. An administrator switches them on when the team needs them.

Data formats: every answer is wrapped as {"meta": {"code": 200}, "errors": [], "data": ..., "pagination": ...}; the data is under data. Weights are in grams, prices and cash on delivery in euros, dimensions in millimetres. Ids of companies, brands, orders, products and shipments are UUID strings; shipping product and combination ids are integers. Fulfilment order statuses are error_validation, concept, received, pending, partically_sent (QLS's spelling) and sent. Stock and purchase order date filters take d-m-Y H:i (e.g. 1-10-2026 00:00); the other date filters take a date or date-time such as 2026-10-01 00:00:00.

Paging: lists return up to 100 entries per page. pagination carries page, pageCount, count and nextPage; the AI asks for the next page while nextPage is true.

Common errors: 401 means wrong user name or password: they are the mijn.pakketdienstqls.nl login. 404 (Niet Gevonden) means an unknown id or a company id that is not yours: take ids from the list tools. 422 or a filled errors list is a validation problem; QLS answers in Dutch.

The connector does not cancel parcel shipments, read QLS invoices or change brands and company settings: there are no tools for that.

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 QLS 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 QLS shipping products can we use for the Netherlands and Belgium, with their price per weight band?"
• "Find the DHL service points near postal code 3011 AB."
• "Create a PostNL parcel for order 1042 to Jan de Vries, Rotterdam, 1,200 grams. Show me receiver, product and weight first."
• "Which fulfilment products have fewer than 20 units available, and what is incoming?"
• "List the fulfilment orders that are still pending or partically_sent from this week."

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