How to Connect Veepee Pink Connect to Microsoft Copilot via MCP

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

Veepee Pink Connect + Microsoft Copilot

Sell on Veepee and Privalia through Pink Connect from an AI agent: orders with lines, addresses, tracking and refunds, offers per sales channel, customer messages, return requests and carriers. Replies, new order messages and return status changes are 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:

PINK_CONNECT_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes once you have the token. You need a seller account on Veepee or Privalia that is managed through Pink Connect, the seller API of the Veepee group marketplaces.

1. Get the API token of your Pink Connect seller account. It is shown in the Pink Connect portal at www.pink-connect.com, or your Veepee marketplace contact sends it to you.
2. Paste it into PINK_CONNECT_TOKEN, on its own, without the word Bearer, quotes or spaces.
3. Install the connector and run pink_connect_list_carriers: it lists the roughly 200 carriers Pink Connect knows and shows that the token works.

Sales channels: every marketplace country site is a shop channel with its own number, for example one for Veepee Italy and one for Privalia Italy. Every order carries its channel, so the AI reads the channel ids from your orders first. Your offers are always listed for one channel at a time.

What it reads: orders with their status, dates, totals and currency, shipping and billing address, order lines (GTIN, SKU, price, tax rate, quantity and the status of each line), delivery details with carrier, tracking number and tracking link, refunds and the requested shipping method; your offers per channel with name, brand, selling and recommended price, discount with its dates, stock, price list and marketplace status; customer messages with subject, text, sender, read state and attachments; return requests with order line, quantity, reason (for example PRODUCT_DAMAGED or SIZE_DONT_FIT), type such as HOMEPICKUP and status; and the carrier list.

How Pink Connect answers: orders come oldest first, so for recent ones the AI always asks for orders changed since a date, up to 100 per page. One order is read by its Pink Connect order id, which is not the marketplace order number; to find an order by the Veepee or Privalia number, the AI searches with the marketplace and its order number together. Customer messages without an order or date filter make Pink Connect scan the whole history, which can take half a minute, so the AI always passes one. Offer statuses come in Spanish, for example "Producto Publicado".

Read-only at install: every tool that is on when you install the connector only reads. Nothing moves money: changing a return status does not refund, and refunds are handled outside this connector.

Switched off at install: pink_connect_reply_notification answers a customer message, pink_connect_create_order_message starts a new conversation on an order that has none yet, and pink_connect_update_return_request moves a return from PENDING to PROCESSING (accepted) or REJECTED, or from PROCESSING to COMPLETE (goods received). They reach real customers, so an administrator turns them on deliberately. Even then the AI shows you the order, the exact message in the customer's language or the return with its new status, and waits for your yes.

Limits: Pink Connect returns at most 100 orders or return requests per call, and one order is about 2 KB, so the AI keeps pages small and filters by date or channel instead of reading everything.

Common errors: 401 means the token is wrong or expired: ask Veepee for a new one. 400 "Invalid page size (max 100)" means a page of more than 100. 422 messages are in Spanish and name the problem, for example "Canal de Venta no puede estar vacío" when the channel id is missing. An unknown id answers with an HTML 404 page.

The connector does not change offers, prices or stock, confirm shipments or upload tracking, cancel orders, or issue refunds.

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 Veepee Pink Connect 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 Veepee and Privalia orders came in since Monday, and which of them have not shipped yet?"
• "Show me the unread customer messages from the last 7 days and the order each one is about."
• "Which return requests are still pending, and what reasons did the customers give?"
• "List my offers on Privalia Italy with fewer than 5 units in stock."
• "Find the Veepee order 87654321 and tell me the carrier and the tracking link."

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