How to Connect weclapp Cloud ERP to Microsoft Copilot via MCP

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

weclapp Cloud ERP + Microsoft Copilot

Read and write weclapp Cloud ERP data: customers, suppliers, contacts and leads, quotations, sales orders, invoices, articles, stock, purchase orders, tasks and time records. Popular ERP for German SMBs.

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:

WECLAPP_TENANT, WECLAPP_API_TOKEN

Step 1 — Get credentials

1. In weclapp, open your user menu → My settings → API and copy the API token into WECLAPP_API_TOKEN. Each user has one token; generating a new one invalidates the old one.
2. Set WECLAPP_TENANT to the first part of your weclapp address only: for acme.weclapp.com, enter acme.
3. Install the connector. It works with weclapp's REST API v2, where customers and suppliers both live under parties.

Permissions follow the user: the token acts as the weclapp user it belongs to. Records that user's role cannot see are missing from the results, and a write the role does not allow is refused with 403. Use a user with read access to sales, CRM and articles, and write access to whatever the AI should change.

What it does: 60 tools that read customers, suppliers, contact persons and leads, quotations, sales orders, sales invoices, recurring invoices, opportunities, articles and stock, and that write back to weclapp:

• create and edit customers, suppliers, contact persons and leads;
• create and edit quotations and sales orders with their positions, change their status, cancel an order and create the invoice for an order;
• edit sales invoices, for example the responsible user or the due date;
• create and edit tasks, add comments to any record and book working time;
• create and edit articles and their sales prices, and book stock in and out;
• create purchase orders to suppliers.

Recurring invoices and opportunities are read-only.

Confirm first: every write changes your live ERP, so the AI reads the record, tells you what will change and waits for your yes. Edits change only the fields that are sent, and a test run (dryRun) lets weclapp check a change without saving it. With the record's version, weclapp refuses a change if someone else edited the record in the meantime. Stock bookings take effect at once, and every invoice created from an order is a new draft invoice. The six delete tools (customers and other parties, quotations, sales orders, tasks, comments and time records) are switched off at install.

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, and the delete tools arrive switched off, as on a new install.

Finding records: the get tools take weclapp's internal id. To find a document by its number, the AI filters the list, for example orderNumber-eq=SO-1042 or invoiceNumber-eq=RE-1042. Unpaid invoices are paymentStatus-eq=OPEN, and credit notes are left out when adding up revenue. Asking only for the fields you need keeps large lists small and fast.

Limits: lists return up to 1,000 rows per page. weclapp has no fixed rate limit, but under heavy load it queues requests and answers 429 after 30 seconds in the queue.

Recurring invoices: this resource is not part of weclapp's published API description. If listing recurring invoices returns 404 on your tenant, it is not available there.

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 weclapp Cloud ERP 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

• "List all unpaid invoices over €1,000 that are past their due date."
• "Create a quotation for Müller GmbH with 20 units of article A5101 at the list price, and show it to me before saving."
• "Book 3 hours for me today on sales order SO-1042, note: installation on site."
• "Add a task for Anna to call ACME about their open quotation by Friday."

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