How to Connect Droppery to Microsoft Copilot via MCP

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

Droppery + Microsoft Copilot

Droppery dropshipping from an AI agent: the supplier products connected to your webshop with purchase and retail prices, stock and delivery times, shipping rates per country, and orders with payment status, supplier shipping status and track and trace. Read-only.

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:

DROPPERY_API_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a webshop account on Droppery, the European dropshipping platform that connects webshops with suppliers.

1. Sign in to the Droppery platform at platform.droppery.io with your webshop account.
2. Open API token in the menu, create a token and copy it right away: Droppery shows it only once.
3. Paste it into DROPPERY_API_TOKEN. It is sent as a Bearer token, so do not add the word Bearer yourself.
4. Install the connector and run droppery_browse_products with size 1. If it returns a product and the total count, the token works.

What it reads: the products of the suppliers connected to your shop with name, brand, supplier, SKU, EAN, stock, purchase price, suggested retail price (both also as discounted price), tax rate, delivery days, visibility, categories, attributes and variants; one product in full with description, images, dimensions, weight, country of origin and shipping rates per country; and one order with date, payment status, shipping address, order lines and, per supplier, the shipping status, carrier and track and trace link.

Use the Droppery order id: an order is read by the number Droppery shows in its own order list, for example 102057, not by the order number of your webshop or marketplace. With that number Droppery answers 404. The API has no order list, so take the id from the Droppery platform or from the system that placed the order.

No product search: Droppery cannot search or filter the product list. The AI pages through it, at most 100 products a page, and filters the result itself.

Prices: the supplier price is what Droppery charges you, excluding VAT; the retail price is the supplier's suggested consumer price, including VAT. The AI keeps the two apart when it works out a margin.

Read-only: there are no write tools, so nothing is switched off or needs your confirmation. Orders are placed by your webshop integration; the connector does not place orders or move money.

Common errors: 401 Unauthenticated means a missing or revoked token: create a new one under API token. 404 means the id does not exist for your shop, often a webshop order number instead of the Droppery id. 422 lists the invalid parameters, for example more than 100 products per page.

The connector does not list or place orders, change products, prices or stock, or connect new suppliers to your shop.

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

• "What is the track and trace link of Droppery order 102057, and has every supplier shipped their part?"
• "Which of my Droppery products have fewer than 5 units in stock?"
• "What does it cost to ship product 48213 to Belgium, Germany and France?"
• "Compare purchase price and suggested retail price of my products and show me the ten with the smallest margin."
• "Which of my supplier products take more than 3 days to deliver?"

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