Summary
Veeqo inventory and shipping software: orders from all stores, products and variants, stock levels per warehouse (read and update), allocations and shipments with tracking, purchase orders, customers and suppliers. API key.
Guided setup
Connect Veeqo to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Veeqo in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Veeqo
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Veeqo, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Veeqo + Microsoft Copilot
Veeqo inventory and shipping software: orders from all stores, products and variants, stock levels per warehouse (read and update), allocations and shipments with tracking, purchase orders, customers and suppliers. API key.
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:
VEEQO_API_KEY
Step 1 — Get credentials
Setting up takes about 2 minutes.
- In Veeqo open Settings, Employees (Users in some accounts) and open the user the AI should act as.
- Generate (or refresh) the API key of that user and copy it into
VEEQO_API_KEY.
The key is sent in the x-api-key header and can do what that user may do, so a user with a limited role limits the connector too.
Where to start: veeqo_get_company shows the account and its plan. veeqo_list_orders with status awaiting_fulfillment lists what is waiting to ship; veeqo_get_order shows one order with its allocations.
Orders: veeqo_list_orders, veeqo_get_order, veeqo_create_order, veeqo_update_order, veeqo_add_order_note. veeqo_cancel_order is installed switched off. For a new order fetch the ids first: veeqo_list_stores (channel_id), veeqo_list_customers or veeqo_create_customer, veeqo_list_delivery_methods and the sellable ids from veeqo_list_products.
Shipping without buying labels: allocate stock with veeqo_create_allocation, then record the parcel with veeqo_create_shipment (carrier id and tracking number); Veeqo marks the order shipped and passes the tracking number to the sales channel. veeqo_get_tracking_events reads the events of labels bought in Veeqo. veeqo_delete_shipment is installed switched off. Buying shipping labels and rates is not part of this connector.
Products and stock: veeqo_list_products, veeqo_get_product, veeqo_create_product, veeqo_update_product. Stock belongs to a sellable (a product variant) in a warehouse: veeqo_get_stock_entry reads it, veeqo_update_stock_entry sets the physical level as an absolute number. Warehouses: veeqo_list_warehouses, veeqo_get_warehouse.
Purchasing (paid plans): veeqo_list_purchase_orders, veeqo_get_purchase_order, veeqo_create_purchase_order (a draft by default), veeqo_list_suppliers, veeqo_get_supplier, veeqo_create_supplier. Receiving stock against a purchase order is left to the Veeqo app, because the API adds received quantities each time it is called.
Customers: veeqo_list_customers, veeqo_get_customer, veeqo_create_customer, veeqo_update_customer.
Ids: an order has an id (used here) and a number (shown to people). A product has sellables; the sellable id is what order lines, stock entries and purchase order lines use. Order statuses: awaiting_payment, awaiting_stock, awaiting_fulfillment, shipped, on_hold, cancelled, refunded.
Paging and limits: lists take page and page_size (at most 100); the total is in the X-Total-Count header, shown as _headers. Veeqo allows 5 requests per second per key with a bucket of 100, then answers 429. Times are UTC; prices are in the currency of the company.
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 showsYOUR_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.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - 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.
- Try it in the agent's Test pane: ask for something that needs the
Veeqotools. - 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
| Tool | What it does |
|---|---|
veeqo_get_company | Read the Veeqo company behind the API key: name, settings (currency, dimension and weight units), billing plan and the features the plan… |
veeqo_list_orders | List orders, newest first (highest id first): id, number, status, created_at, due_date, shipped_at, subtotal_price, total_tax, total_price… |
veeqo_get_order | Read one order: status, dates, prices and taxes, payment, customer with billing address, deliver_to address, delivery method, store… |
veeqo_create_order | Create an order in Veeqo for a store (channel), a customer and a delivery address. Fetch the ids first: veeqo_list_stores… |
veeqo_update_order | Update an order: delivery address, delivery method, due date, discount or line items. Only the fields given change. Line items given… |
veeqo_add_order_note | Add an internal (employee) note to an order, visible to the team in Veeqo but not to the customer. Returns the note |
veeqo_cancel_order | Cancel an order, optionally with a reason and an email to the customer. The order status becomes cancelled and allocated stock is released.… |
veeqo_create_allocation | Allocate stock of a warehouse to an order, as the step before shipping. Returns the allocation with its id, which veeqo_create_shipment… |
veeqo_create_shipment | Record the shipment of one allocation of an order, which marks it as shipped and, where the store syncs tracking, sends the carrier and… |
veeqo_delete_shipment | Delete a shipment record, which sets its allocation back to not shipped. Installed switched off |
veeqo_get_tracking_events | Read the tracking events of a shipment whose label was bought in Veeqo: status, description, location and time of each event. Shipments… |
veeqo_list_products | List products with their variants: id, title, description, brand, main image and sellables, each with id (the sellable id), sku_code… |
veeqo_get_product | Read one product with all its sellables (variants): SKU, barcode, prices, weight and dimensions, stock entries per warehouse, images and… |
veeqo_create_product | Create a product with one or more variants (title, SKU code and price each). Returns the product with the sellable ids of its variants.… |
veeqo_update_product | Update a product and its variants: title, description, notes or variant fields such as price, cost price, SKU and barcode. Only the fields… |
veeqo_get_stock_entry | Read the stock of one sellable in one warehouse: physical_stock_level, allocated_stock_level, available_stock_level, incoming_stock_level… |
veeqo_update_stock_entry | Set the physical stock level of one sellable in one warehouse (a new absolute number, not a change), and optionally its shelf location.… |
veeqo_list_warehouses | List the warehouses (locations) of the company: id, name, address, phone and whether it is the default. Read-only |
veeqo_get_warehouse | Read one warehouse: name, full address, contact details and settings. Read-only |
veeqo_list_purchase_orders | List purchase orders with supplier, destination warehouse and line items (purchase_order_product_variants with quantity, cost and received… |
veeqo_get_purchase_order | Read one purchase order from the database: number, state, supplier, destination warehouse, expected date, currency, totals and line items… |
veeqo_create_purchase_order | Create a purchase order for a supplier and a destination warehouse, as a draft unless state says otherwise. The number is generated by… |
veeqo_list_customers | List customers: id, email, phone, customer_type, full name, notes, billing address and shipping addresses. The total number of rows is in… |
veeqo_get_customer | Read one customer: contact details, notes, billing address, all shipping addresses with their ids, and order counts. Read-only |
veeqo_create_customer | Create a customer with an email, a type (retail or business) and optionally phone, notes and a billing address. Returns the customer with… |
veeqo_update_customer | Update a customer: email, type, phone, notes or billing address. Only the fields given change |
veeqo_list_suppliers | List suppliers: id, name, address, sales and accounting contacts, currency_code and purchase order counts. Needs a paid Veeqo plan.… |
veeqo_get_supplier | Read one supplier: name, address, contacts, currency, bank details on file and purchase order counts. Needs a paid Veeqo plan. Read-only |
veeqo_create_supplier | Create a supplier with a name and optionally address, sales contact and currency. Returns the supplier with its id. Needs a paid Veeqo plan |
veeqo_list_stores | List the stores (sales channels) connected to Veeqo: id, name, type (Shopify, Amazon, eBay, direct and others), currency and default… |
veeqo_list_delivery_methods | List the delivery methods of the company: id, name and cost. The id is the delivery_method_id of an order. Read-only |
Example prompts
- "Which orders are awaiting fulfillment, oldest first?"
- "What is the stock of SKU MUG-BLU-350 in each warehouse?"
- "Set the stock of SKU MUG-BLU-350 in the main warehouse to 120."
- "Mark order 45123987 as shipped with DPD tracking 15501234567890."
- "Create a draft purchase order to supplier Nordic Ceramics for 200 MUG-BLU-350."
FAQ
Where does the API key come from? In Veeqo open Settings, Employees (Users in some accounts), open the user the AI should act as and generate or refresh the API key. The key can do what that user may do, so a user with a limited role limits the connector too.
What does it cover? Orders from all connected stores with notes, products and variants, stock per warehouse (read and set), allocations and shipments with tracking numbers, tracking events, purchase orders (paid plans), customers, suppliers, stores and delivery methods. Buying shipping labels and rates is not included, and receiving stock against a purchase order stays in the Veeqo app.
Which tools install switched off? veeqo_cancel_order and veeqo_delete_shipment. Switch them on on the connector page only if the AI should use them.
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
Was this guide helpful?