Connect ManoMano to Microsoft Copilot via MCP

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

ManoMano + Microsoft Copilot

Sell on ManoMano, the European DIY and garden marketplace, from an AI agent: orders with acceptance, shipment and refunds, offer prices and stock, competitiveness against other sellers, catalog lookups by EAN, ManoFulfillment stock and customer invoices. One install per seller contract.

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:

MANOMANO_API_KEY, MANOMANO_SELLER_CONTRACT_ID

Step 1 — Get credentials

1. Sign in to the ManoMano Toolbox at https://toolbox.manomano.com with a user that has the Admin role.
2. Open Settings > API keys, click Create API key, give it a name such as AnythingMCP and click Generate API key. Copy the key right away: ManoMano shows it only once. Paste it into MANOMANO_API_KEY.
3. Enter your seller contract id in MANOMANO_SELLER_CONTRACT_ID. It is a number shown in the Toolbox, for example 110841.
4. Install the connector and start with manomano_list_orders.

One install per contract: ManoMano creates one seller contract per platform (manomano.fr, .es, .it, .de and .co.uk) and delivery mode, so a seller on several platforms has several contracts. Install the connector once per contract and name each install after it, for example ManoMano FR. The contract id is added to every call, and the key is sent only to ManoMano.

Order workflow: a new order is PENDING. Accepting it moves it to PREPARATION; refusing it refunds the customer (REFUNDING, then REFUSED). Shipping records the carrier, the tracking number and URL and the products in the parcel, once per parcel, and the order becomes SHIPPED. A refund covers some or all products (REFUNDING, then REFUNDED). For the daily to-do list, the AI lists the orders in PENDING and in PREPARATION, and it reads an order before shipping or refunding it, because both need each product's seller_sku and quantity.

Confirm first: accepting, refusing, shipping and refunding orders, changing, unfreezing and replacing offers, and uploading invoices act on the live marketplace. Before each of these the AI shows you what will change (the order, the products and quantities, the tracking number, the SKUs with old and new price or stock, the document) and waits for your yes. Refusals and refunds cannot be undone.

Prices and stock: manomano_update_offers changes the price, the stock or both of existing SKUs. By default the new values are frozen, so later product feed imports no longer overwrite them, until manomano_unfreeze_offers hands them back to the feed. ManoMano applies the update in the background: the AI checks it with manomano_list_offers and the returned request_id (IN PROGRESS, ERROR with the errors, or COMPLETED). manomano_upsert_offers, which creates offers or replaces them completely, is switched off at install.

Competition, catalog and fulfillment: compare chosen SKUs with the best offer on the product, or list every offer whose competitive situation changed in a date range. Look up up to 200 EANs at once to see whether a product is already in the ManoMano catalog and whether you can publish an offer on it. ManoFulfillment warehouse stock is only available on a ManoFulfillment contract.

Customer invoices: the AI lists the invoices customers are waiting for, oldest first. You have 3 working days after shipment to provide one. The AI uploads the PDF from a URL; each upload is added next to earlier documents, and the customer is notified.

Limits: about 250 order requests and 200 offer requests an hour per API key; beyond that ManoMano answers 429. Orders come in pages of at most 50. The connector works on the live API, not on ManoMano's sandbox.

Common errors: 401 means ManoMano refused the key: check it, or create a new one in the Toolbox (a deleted key stops working at once). 403: the key works but may not act on this contract; check that the contract id belongs to the seller account that created the key. 400: check that the contract id is your numeric seller contract id. 429: too many requests; wait before trying again.

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 ManoMano 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 ManoMano orders are still pending, and which orders in preparation are older than two days?"
• "Ship order M240915123 with Colissimo, tracking number 6A12345678901, all products in one parcel."
• "Set the price of SKU DRILL-18V to 89.90 euros and its stock to 25, then check that the update went through."
• "For these five SKUs, am I the best offer on ManoMano? Show me who beats me and at what price."

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