Integrate Monta MCP server into your Slack workspace for instant access to your AI agent.
Tools that your AI agent can use through this MCP server to interact with Monta
Validate a delivery address before submitting it, for example ahead of Create Order or Update Order. Monta returns structured error codes when the address is invalid; a complete address also needs a recipient (Company or Last Name), Postal Code, and House Number. See the documentation
Change an existing order by its ID, for example to correct a customer's delivery address before it is picked. Call this directly with the order ID and the fields to change. When changing the delivery address, first read the current address with Get Order, then call this with the full address plus your change, since Monta replaces the entire address (it needs at least Street, City, and Country Code). Monta rejects address changes once picking has started (error 17) or after the order has shipped (error 19). See the documentation
Update an existing inbound forecast group's details by its reference: its comment, warehouse, or expected delivery date. The forecasts, supplier, and stock-allocation flag are set at creation and cannot be changed here. See the documentation
List orders whose status changed since a specified date and time, including orders deleted since then. Use this for reliable bulk order syncing; for cursor-based incremental polling of individual change events, use List Order Events Since ID instead. See the documentation
List the shipping labels of an order. Use this to retrieve the label file names, typically after generating labels with Create Shipping Label. See the documentation
List the return labels for an order (labels for inbound returns), as opposed to outbound shipping labels. Use this when handling a customer return that needs a prepaid inbound label; see List Order Returns for the associated return records. See the documentation
List the expected (forecasted) returns for an order, as opposed to the actual return records from List Order Returns. Use this to anticipate inbound returns before they physically arrive. See the documentation
List products whose stock changed since a specified date and time. See the documentation
List the return records for an order. Use this to see all returns registered against an order. See the documentation
Retrieves available options for the Order ID field.
List order events for an order. See the documentation
List order change events created after the provided cursor ID, which is Monta's recommended method for reliable status-change polling. Use this for incremental syncing across all orders; see List Order Events for a single order's history or List Updated Orders for datetime-based bulk syncing. See the documentation
List the colli (parcels) that make up an order. Use this to inspect the parcel and tracking breakdown for a shipment, for example after registering parcels with the Add Order Colli action. See the documentation
List the batch (lot) lines shipped for an order. Use this for batch traceability when you need to know which lots were used to fulfill an order. See the documentation
List inbound shipments expected at the warehouse. Use this to review incoming stock, paging forward with the Since ID cursor to walk through large result sets; relate to List Inbound Forecast Groups for grouped forecast data. See the documentation
List all inbound forecasts for a given product SKU across groups. Use this to check expected incoming stock for a SKU. See the documentation
List inbound forecast groups matching the provided filters. You must supply at least one filter (Created Since, Created Until, Approved, SKU, or Reference). Use this to find group references for Get Inbound Forecast Group, Update Inbound Forecast Group, or Delete Inbound Forecast Group. See the documentation
List inbound forecast change events created after the provided cursor ID. Use this for reliable incremental syncing of inbound forecast changes by repeatedly polling with the last event ID. See the documentation
Get a return by ID. See the documentation
Get an order by ID. See the documentation
Retrieve a single inbound forecast from a group by reference and SKU. See the documentation
Retrieve an inbound forecast group and its forecasts by reference. See the documentation
Anonymize an order for GDPR erasure. This permanently removes personal data and cannot be undone. See the documentation
Download a single shipping label file for an order and save it to the /tmp directory. See the documentation
Delete an inbound forecast group, or a single SKU within it when a SKU is provided. See the documentation
Generate a shipping label for an order in a supported output format (pdf or zpl). Use this when an order is ready to ship and needs a carrier label. See the documentation
Create an RMA (return merchandise authorization) link for an order, so a customer can start a return. Review existing returns for the order with List Order Returns. See the documentation
Create a new order in Monta for fulfillment. Provide the recipient's delivery address (which needs a Company or Last Name) and at least one order line; validate the address first with Validate Address if needed. See the documentation
Create a new inbound forecast group describing stock expected at the warehouse. Manage the group afterwards with Update Inbound Forecast Group, Get Inbound Forecast Group, or Delete Inbound Forecast Group. See the documentation
Cancel (delete) an order. Monta rejects this once picking has started (error 18), after the order has shipped (error 19), or when returns exist (error 25). See the documentation
Approve multiple inbound forecasts at once by their IDs. See the documentation
Register a collo (parcel) on an order, including its dimensions and tracking details. Use this to record how an order was packed; inspect the result with List Order Colli. See the documentation