Connect Billbee to Microsoft Copilot via MCP

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

Billbee + Microsoft Copilot

Let your AI work with your Billbee order management: find orders from all your marketplaces and shops, look up articles by SKU or EAN with price and stock, check a customer's order history, and act on orders: set the order state, add tracking numbers, book labels through the carriers connected in Billbee, update stock, tag orders, change order and article fields and create invoices. With an API key, your login email and an API password.

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:

BILLBEE_API_KEY, BILLBEE_LOGIN_EMAIL, BILLBEE_API_PASSWORD

Step 1 — Get credentials

1. Sign in to Billbee and open Settings → Billbee API (Einstellungen → Billbee API in the German interface). In the general settings there, enable API access and set an API password. This is a separate password just for the API, not the one you log in with.
2. Request an API key from Billbee: use their API request form or write to [email protected] and describe briefly what you want to connect (here: your AI reading orders through AnythingMCP). Billbee sends you the key.
3. Put the key into BILLBEE_API_KEY, the email address you sign in to Billbee with into BILLBEE_LOGIN_EMAIL, and the API password from step 1 into BILLBEE_API_PASSWORD.
4. Install the connector. There is no Authorize with Provider step: every call sends the API key in the X-Billbee-Api-Key header, plus your email and API password as HTTP Basic auth.
5. Start with billbee_list_shipping_providers: it needs no parameters and lists the shipping providers set up in your account. If it answers, all three values work.

Three values, all required: Billbee rejects a call that carries only the API key, or only email and API password. All three must be set on the connector.

Staying signed in: there are no tokens to renew, the connector sends the three values with every call. If you change the API password in Billbee or get a new API key, update BILLBEE_API_PASSWORD or BILLBEE_API_KEY on the connector page.

Reading and writing: 9 of the 17 tools only read orders, articles, customers, shipping providers and stock locations. The other 8 change your live Billbee account, and Billbee passes most changes on to the connected shops and marketplaces. All 17 install switched on. For a read-only setup, switch off the write tools on the connector page; you can also disable single read tools, for example billbee_list_customers and billbee_get_customer_orders if the AI should not see customer data.

Write tools:

• billbee_set_order_state sets the order state, for example 3 paid, 4 shipped, 8 canceled or 13 packed. The shop or marketplace may email the buyer.
• billbee_add_shipment_to_order stores a tracking number created elsewhere; it neither creates a label nor changes the state. billbee_ship_order_with_label books a real, billable label with a carrier connected in Billbee (DHL, DPD, GLS, Deutsche Post and others) on your own carrier contract; providerId and productId come from billbee_list_shipping_providers, and the AI asks you before booking.
• billbee_update_stock sets the absolute stock of an article by SKU, not a change; with several stock locations it needs stockId from billbee_list_stocks. Billbee sends the new stock on to your shops and marketplaces.
• billbee_add_order_tags adds tags to an order. billbee_update_order and billbee_update_product change only the fields passed, with the field names that billbee_get_order and billbee_get_product return, such as SellerComment or Price.
• billbee_create_invoice creates the invoice of an order with your invoice template, at most once per order every 5 minutes, and can return the PDF.

The write tools take Billbee's internal order id, not the shop order number: billbee_get_order_by_extref finds the id for a marketplace order number.

Orders: billbee_list_orders filters by order date (minOrderDate, maxOrderDate) and by last change (modifiedAtMin, modifiedAtMax), with dates in ISO 8601 such as 2026-01-01. billbee_get_order returns the full order with items, addresses, payment and shipping details by its Billbee order id. billbee_get_order_by_extref finds an order by the order number of the marketplace or shop, such as an Amazon or eBay order number. Order states come back as numbers.

Articles and customers: billbee_get_product looks up an article by its Billbee id, or by SKU or EAN when lookupBy is sku or ean, and returns prices and stock. billbee_list_products can be limited to articles created after a date (minCreatedAt). billbee_list_customers has no search, so finding a customer by name means paging through the list; with the customer id, billbee_get_customer_orders lists that customer's orders.

Pages and rate limits: list tools return up to 250 rows per page (pageSize), with Page, TotalPages and TotalRows in the answer, and the AI asks for the next page until it reaches the last one. Billbee allows 2 requests per second per API key and user and answers 429 above that: wait a moment and try again. Billbee charges for API usage above a free allotment, so narrow date ranges and modifiedAtMin are better than listing everything again and again.

Common errors: if Billbee refuses the credentials, check that all three variables are set, that API access is enabled under Settings → Billbee API, and that BILLBEE_API_PASSWORD holds the API password, not your login password. 429 means the limit of 2 requests per second was hit.

The connector does not create or delete orders, does not create or change customers, and does not create or delete articles.

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 Billbee 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 orders came in over the last 7 days, and which of them have not shipped yet?"
• "Find the order with the marketplace order number 302-1234567-1234567 and show me the items, the delivery address and the payment details."
• "How many units of SKU ABC-123 do we have in stock, and what is the selling price?"
• "List all orders of Billbee customer 4567 with date and total, newest first."
• "Mark the Amazon order 302-1234567-1234567 as shipped and add the DHL tracking number 00340434161234567890."
• "Create a DHL label for the eBay order 14-12688-90311 through Billbee, then create its invoice."

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