Connect Kaufland to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Kaufland Marketplace, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Kaufland Marketplace + Microsoft Copilot

Kaufland Marketplace (formerly real.de) seller API: orders and their units, storefronts, units, tickets and warehouses. HMAC-signed requests — the signature covers the method, URL, body and a timestamp.

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:

KAUFLAND_CLIENT_KEY, KAUFLAND_SECRET_KEY

Step 1 — Get credentials

Getting credentials

1. You must already be a Kaufland Marketplace seller. In the Seller Portal open Settings → API keys and create a key pair.
2. You receive a Client Key (public, identifies you) and a Secret Key (never sent — it signs the request). Set KAUFLAND_CLIENT_KEY and KAUFLAND_SECRET_KEY.

The secret never travels. Kaufland does not accept a bearer token: every request carries Shop-Client-Key, Shop-Timestamp and Shop-Signature, where the signature is an HMAC-SHA256 over the canonical string

<METHOD>\n<FULL URL INCLUDING QUERY>\n<BODY>\n<UNIX TIMESTAMP>

…(continued in the in-app connector instructions)

Tickets, returns and tracking: besides the ticket list, the connector reads one ticket with its conversation and the newest messages across all tickets, and lists returns and the returned items one by one with their status and reason, for example the items that have arrived and wait for your decision. Two tools write, and both are switched on at install: kaufland_add_ticket_message sends your answer to the buyer in the ticket, and kaufland_add_tracking_to_order_unit adds a carrier code and tracking number to an order unit already marked as sent, so the buyer can follow the parcel. The AI shows you exactly what will be sent and waits for your yes before either call. To keep the connector read-only, switch both off on the connector page.

Already installed? The new tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your credentials and any tools you added yourself stay as they are.

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 Kaufland Marketplace 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

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