Skip to main content
Læs siden på dansk The Webshipper connector gives your AI access to the shipping from your webshop in Webshipper: orders with status and error message, shipments with tracking, shipping costs per carrier, shipping rates, drop points, carriers, order channels and returns. It can also book a shipment for an order, correct an order before it ships and create a manual order, always behind a preview that you must confirm. You connect with your account name and an API token that you create yourself in Webshipper, and your AI never sees the token itself.
Read + guardrailed write. 12 tools only read. The 3 write tools change nothing in Webshipper without an explicit confirmation (confirm: true). Without it, you only get a preview. Booking a shipment buys postage from the carrier, and the carrier or the shop can notify the recipient. An administrator can set the individual user to Read only. See Actions & guardrails.

Access

Read + guardrailed write. Read only can be chosen per user

Authentication

Account name and API token from Webshipper

Hosting

Hosted in the EU · Frankfurt
  • Price: 299 DKK/month excl. VAT (€39/month if you have chosen the EU · EUR market in the portal). No lock-in, cancel at any time. The price covers 1 user and 1 Webshipper account. Each extra user and each extra account costs 149.50 DKK/month excl. VAT. See Pricing. Webshipper is also included in the Consile Studio membership and the free edition.
  • One account per connection: an API token belongs to one Webshipper account (for example myshop.webshipper.io). If you have several accounts, for example one per brand or country, you connect one agreement per account. Each extra agreement gets its own address, for example https://mcp.consile.ai/webshipper-2/mcp. See Multiple agreements.
  • Endpoint: https://mcp.consile.ai/webshipper/mcp (your own named connector in your AI).

Prerequisites

1

Subscription

An administrator buys the connector in the portal. See Buy a connector.
2

Your AI connected

3

Webshipper Pro or Advanced

API access comes with Webshipper Pro and Advanced. On another plan you cannot create the API token the connector uses.
4

Webshipper connected

Create an API token in Webshipper under Settings → Access and tokens, and paste it in the portal together with the account name. See Connect Webshipper.
5

Access for each user

Whoever buys Webshipper automatically gets the included access. If more colleagues need Webshipper in their AI, an administrator gives them access on the person’s page under Team and chooses their access level at the same time (see Access level per user). Each extra user costs 149.50 DKK/month excl. VAT. If you have the Consile Studio membership, an administrator instead gives one membership licence per person, and it also covers Webshipper. See Team.
Were you a customer before 2026-11-17? If your organization has a membership or a free edition from before Webshipper was added, Webshipper’s tools are switched off until an administrator switches them on under Tools. New customers get both the read and the write tools switched on from the start.

What can it do? (tools)

You do not need to know the tool names. You ask in natural language, and your AI picks and calls the right tool itself. Each tool is called webshipper__<tool> (for example webshipper__search_orders); in the tables below the names are shown without the prefix. The connector provides 15 tools in total: 12 read-only and 3 guardrailed write tools. A user on Read only only gets the 12.

Reading (12 read-only)

Orders Shipments & tracking Shipping rates & costs Drop points, setup & returns

Writing (3 guardrailed tools)

These 3 tools are the only ones that change anything in Webshipper. A call without confirm: true never changes anything, but shows exactly which change would be sent. Normally your AI shows you the preview and only calls again with confirm: true once you have said yes. The Extra lock column shows the tools where the confirmation must also match the preview (see How the guardrail works).

Building on top of it yourself? See the API reference

Full reference with all 15 tools, arguments, pagination, guardrail fields and errors.

How the guardrail works

  1. All 3 write tools are dry-run by default. A call without confirm: true never changes anything in Webshipper. You get a preview of exactly the change that would be sent. For bookings and corrections, it also shows the order as it is now.
  2. The change is only made with confirm: true. There are no exceptions.
  3. Bookings and corrections must match the preview. create_shipment and update_order also require a check value from the preview. If the order has changed in Webshipper between the preview and the confirmation, the call is refused, and nothing is changed. It always takes two calls.
  4. Only orders that can ship. An order that is already dispatched, partly dispatched, cancelled or locked in Webshipper can be neither booked nor corrected. An order on hold must be released with update_order before it can be booked. This stops an order that has already shipped from being booked again.
  5. Nothing is deleted or cancelled. The connector cannot delete or cancel orders and shipments, print labels or order a pickup. You do that yourself in Webshipper.
  6. An unknown outcome is stated plainly. If a write gets no answer from Webshipper, the error tells your AI that the outcome is unknown and asks it to check in Webshipper before trying again.
A booking costs postage. Once create_shipment is confirmed, the shipment is bought from the carrier, and the recipient may have been notified. Deleting the shipment in Webshipper afterwards does not always cancel it with the carrier. Read the preview before you say yes.
Read the full confirmation model, which applies across all write connectors, under Actions & guardrails. If you want an administrator’s yes before specific writes, use Approvals. A rule on a write tool applies to both the preview and the confirmation.

Access level per user

An administrator chooses the access level for each user in the portal under Team: click the user’s name, and for Webshipper choose between None, Read only (12), Full access (15) and Custom, where you choose exactly the tools the user gets (see Custom access). The numbers count the tools the organization has switched on.
  • Both levels cost the same.
  • If a user is on Read only, Consile blocks all write operations on the server for that user: the write tools do not show in the user’s AI, and a call to them is refused without anything being changed.
  • The connection to Webshipper belongs to the company, so colleagues with Full access can still write.

Try asking

“Which orders failed in Webshipper today, and why?”
“Show the orders that are on hold, and how long they have been waiting.”
“Where is the parcel for order 1001, and when was it last scanned?”
“Find the shipment with tracking number 00370712345678901234, and show its events.”
“What did we spend on shipping per carrier in October, and what did customers pay?”
“Which parcel shops are closest to Vestergade 10, 8000 Aarhus C?”
“Change the delivery address on order 1001 to Nørregade 5, 1165 Copenhagen K.” (you get a preview and must confirm)
“Book the shipment for order 1001 with the order’s own shipping rate. Show it to me first.”
The shop’s own order number is not the same as Webshipper’s id for the order. Feel free to mention the order number in the question. Your AI finds Webshipper’s id itself with search_orders.

Limitations

  • Writing is guardrailed, not unrestricted. The 3 write tools only work behind the confirmation lock above. The guardrail consists of safe defaults in the connector and is not an absolute guarantee.
  • A booking cannot be taken back. Postage is bought once a shipment is booked. If it must be cancelled, you do that in Webshipper or with the carrier.
  • Not in this version. Labels and other documents as files, printing, pickups, returns as writes, notes, deleting and cancelling, and setting up carriers, shipping rules and webhooks.
  • Credentials are never shown. The shop’s access tokens, the carrier agreements’ credentials, documents such as labels and packing slips, and images from returns are never sent to your AI.
  • Personal data. Orders and shipments contain your customers’ addresses. Lists show name, company, postal code, city and country. A single order or shipment also shows phone and e-mail, which customer service needs.
  • The token’s permissions. If the token lacks access to an area in Webshipper, for example shipments, the tools that use that area fail with an explanatory message. The other tools keep working.
  • One page at a time. Searches return 30 results per page. Your AI asks for the next page itself when there may be more. A shipping cost summary reads at most 1,500 shipments; if the period is larger, your AI asks for a shorter period.
  • Webshipper’s call limit. Webshipper allows about 2 calls per second per API token, and the limit is shared by all users of the same connection. If your AI hits it, it is told to wait a little.
  • No stored data. Everything is fetched and written live when you ask. Consile stores no order or shipment data.
Is something not working as expected? See Troubleshooting.