How to Connect Flour to Microsoft Copilot via MCP

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

Flour + Microsoft Copilot

Flour cloud POS and merchandise management (Germany), read-only: articles with prices and stock per warehouse, stock movements, receipts, invoices and other documents, sold articles per period and till, business partners, cash register journals, stocktakes, branches and points of sale.

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:

FLOUR_API_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes once you have the token. You need a Flour account and a REST API v3 token, which Flour issues on request.

1. Write to [email protected] from the account owner's e-mail address and ask for a REST API v3 token for your Flour account.
2. Paste only the token into FLOUR_API_TOKEN, without the word Bearer, spaces or quotes. The connector sends it in the Authorization header.
3. Install the connector and run flour_list_stocks: it lists your stocks (warehouses, shop floors, online stock) with their ids and shows that the token works.

What it reads: your stocks, branches and points of sale (cash registers); articles with article number, EAN, manufacturer, sales prices per price list, purchase prices, reorder levels, variants and bundle parts; the stock of each article per stock, both physical (counted) and calculated (after open orders), and its stock movements (goods received, sales, corrections, transfers); sales and purchase documents (receipts and invoices, quotes, orders, delivery notes, credit notes, purchase invoices, purchase orders) with items, VAT breakdown and payment status; the articles sold in a period with quantity and net revenue, also per till; customers and suppliers; cash register journals with opening and closing cash and withdrawals; stocktakes with their counted items; and the statistics saved in your account.

Master data first: the filters work with ids. The AI first reads your stocks and points of sale, then asks for the receipts of one till or the stock in one warehouse. For what sold best it uses flour_get_sold_articles, which already takes credit notes off; for single receipts and invoices it uses flour_list_documents and flour_get_document. flour_find_article finds an article by its article number or by the EAN on the barcode.

Dates and amounts: Flour expects dates in UTC. A German business day starts the evening before in UTC (22:00 in summer, 23:00 in winter), and the AI converts for you. Amounts are in the document currency, usually euro: totalExVat is net, totalIncVat gross.

Short ranges on busy tills: lists come page by page, without a total. A year of receipts can be tens of thousands of documents, and answers over 400 KB are cut, so the AI asks for a day or a week at a time.

Read-only: all 17 tools only read. Nothing changes in your Flour account, so there is nothing to confirm and no tool is switched off at install.

Credentials stay in Flour: payment terminal settings, fiscal TSE data and bank details stored in Flour are removed from the answers and never reach the AI.

Limits: Flour allows about 60 requests per minute per token. After a 429 the AI waits a minute before trying again.

Common errors: 401 means the token is wrong or was revoked: ask [email protected] for a new one. 429 means more than about 60 requests in a minute. An answer that is cut off means the date range was too large: narrow it.

The connector does not ring up sales, create or change articles, documents or business partners, book stock or close tills: it only reads.

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 Flour 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 articles sold best last week across all tills, by quantity and by net revenue?"
• "Which articles have 5 or fewer left in stock, and when did we last receive goods for them?"
• "Show me yesterday's receipts from the till in our Freiburg shop with the total including VAT."
• "Find the article with EAN 4006381333931 and show me its price and stock per warehouse."
• "How much cash was in the till at closing on Saturday, and were there any withdrawals?"

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