Shipping is one of the biggest costs in an online store and one of the least analysed, because the numbers live in the fulfilment tool rather than the store or the ad accounts. ShipStation is now a live MCP integration in Cogny, so an agent can finally put carrier spend next to revenue and ad spend.

It came from a customer wish in Settings → MCPs For Cogny. Our research pass held it for a human because ShipStation runs two API generations with different authentication, so we checked the details against ShipStation's published OpenAPI spec before building: the V2 API at api.shipstation.com/v2, one API-Key header, 200 requests per minute per account.

TL;DR

ShipStation is live now. Connect it with a V2 API key from your warehouse Settings → Cogny Managed MCPs.
12 tools across shipments, labels, fulfillments, carriers, warehouses, products and inventory. All of them are reads — no labels are bought or voided and no shipments are created or changed.
Two summary tools do the heavy lifting inside the proxy: get_shipping_cost_summary totals label count and carrier cost (shipping + insurance) per day, ISO week or month, split by carrier, service, domestic vs international and return labels; get_shipment_volume_summary counts shipments by status, store and destination country with order value (amount_paid) and shipping charged (shipping_paid).
Money is summed per currency and never converted. Voided and test labels are left out of cost and counted separately.
The ecommerce scheduled template now recommends itself when ShipStation is connected, and uses it for the fulfilment side when a store platform is connected too.
Included in Cogny Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.

What you can do with it

Area	What Claude can do
Shipping cost	Total carrier spend per day/week/month; split by carrier, service, domestic vs international; count return labels and their cost; average cost per label
Order volume	Count shipments per period by status (pending, processing, label purchased, cancelled), by store and by destination country; sum order value and shipping charged
Shipments	List and filter by status, created/modified date, store, order number, recipient, item keyword or tag; read a full shipment with items and addresses
Labels & tracking	List labels with cost, carrier, service and tracking status; read the tracking events for one label
Fulfilment	List fulfillments with ship date and delivery date, for transit-time checks per carrier and country
Setup & stock	Connected carriers and their services, ship-from warehouses, products, and inventory levels when stock is managed in ShipStation

Some questions it can now answer: "What did we spend on shipping per month this year, and which carrier got more expensive?" "Are we charging customers less for shipping than the labels cost us?" "How many orders are still pending from last week?" "Which countries are we shipping to most, and is international growing?"

Why the summary tools matter

ShipStation returns labels and shipments a page at a time, and every label carries download links, package details and a rate breakdown. An agent that works out monthly shipping cost by listing labels fills its context with data it doesn't need. The two summary tools run that loop inside the proxy instead: up to 10,000 labels or shipments per call, with a truncated flag that tells the agent to split a longer window by month. The agent gets back a few hundred bytes of totals. If ShipStation's rate limit is hit mid-way, the proxy waits out one short Retry-After and carries on instead of failing the whole summary.

The list tools return slim records by default (IDs, status, dates, cost, carrier, and recipient name with city, postcode and country, without street addresses). Pass full=true when you need ShipStation's complete object.

How to connect it

In ShipStation, open Settings → Account → API Settings and generate a key under the V2 API section (name it e.g. Cogny).
In your warehouse Settings → Cogny Managed MCPs, click Connect on the ShipStation card.
Paste the key.

The key is stored encrypted, scoped to one workspace and sent only as the API-Key header to api.shipstation.com. If ShipStation rejects it, the error tells you whether you pasted a V1 key by mistake. Disconnect any time with one click, and delete the key in ShipStation if you stop using Cogny.

On trust

Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know that all of them read and none of them write. Buying labels costs real money, so label purchase, voiding and shipment edits are deliberately left out of this release. If we add writes later, they will be separately named tools behind Cogny's standard approval gate.

If you ship physical products through ShipStation, connect it from your Cogny dashboard and ask what shipping really cost you last quarter.