How to Connect BricoBravo to Microsoft Copilot via MCP

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

BricoBravo + Microsoft Copilot

Sell on BricoBravo, the Italian DIY and home marketplace, from an AI agent: orders with items, totals, customer and shipping address, filtered by date. Confirming shipment with courier and tracking is included, installed 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:

BRICOBRAVO_API_TOKEN

Step 1 — Get credentials

Setting up takes a couple of minutes once you have the token. You need a seller account on BricoBravo, the Italian DIY, home and garden marketplace, and the API token of its Seller Hub.

1. Get the API token of your shop from BricoBravo: in the Seller Hub at sellerhub.bricobravo.com, or from BricoBravo seller support.
2. Paste it into BRICOBRAVO_API_TOKEN. It is sent in the sh-token header, so do not add the word Bearer.
3. Install the connector and run bricobravo_search_orders with per_page 1. If it returns an order, or an empty list on a brand new shop, the token works.

What it reads: your BricoBravo orders with the Seller Hub order id and the marketplace order number, status, total, creation date, items (EAN, product code, name, price, list price, quantity), invoice data and the shipping data of customer and receiver (name, email, phone, street, postcode, city, province, country). The AI filters orders by creation time and pages through them, 100 per page by default.

Two order numbers: every order has a Seller Hub id (id_order) and a marketplace number such as 1234460505385-01. To read a single order the AI needs the Seller Hub id; with the marketplace number BricoBravo answers with an error list instead of the order. If you only have the marketplace number, the AI finds the order in the list first.

Status and times: 0 paid (to ship), 1 completed, 2 to be refunded, 3 refunded. Times are Italian time.

Orders already imported: the connector asks for all orders, including those an order management system has already picked up, so none are missing from the list.

Switched off at install: bricobravo_mark_shipped. It confirms the shipment of a real customer order with courier, tracking number and tracking URL; called again on a shipped order, it replaces the tracking data, for example after a second dispatch. Couriers include BRT, GLS Italy, SDA, Poste Italiane, TNT, DHL, UPS, FedEx, DPD and more. If your order management system already confirms shipments, use it only for corrections. An administrator turns it on deliberately, and even then the AI shows you the order, courier and tracking and waits for your yes, then reads the order again to check.

Common errors: 401 token NOT valid means a wrong or revoked token: ask BricoBravo for a new one. 404 means BricoBravo does not know the route or the order.

The connector does not refund or cancel orders, change products, prices or stock, or answer customers.

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 BricoBravo 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 BricoBravo orders are paid but not shipped yet?"
• "Show me the BricoBravo orders of the last 7 days with total and delivery province."
• "Find order 1234460505385-01 and tell me what the customer bought and where it has to go."
• "Which orders are waiting for a refund right now?"
• "How much did we sell on BricoBravo in September, and which product sold the most units?"

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