Packing slips that carry no prices: what is in each carton, what it weighs, and what is still to pack. You raise a packing list against an order you name, declare what the order says is in it, and pack goods into named cartons one line at a time with a per-unit weight, each carton carrying a tare weight in whole grams and its outside dimensions in whole centimetres. packing_shortfall reports every line as short, complete, over-packed, or packed and not on the order at all, matched on SKU where there is one and on the description where there is not. carton_report gives tare, net, gross, volume, volumetric and chargeable weight per carton and for the whole shipment at a divisor of 4000, 5000 or 6000 cm3 per kg, because the divisor is a tariff term, not a constant. The slip itself carries no prices at all: the invoice against the same order is a different document, and no currency symbol reaches the rendered slip. Nothing derived is stored.
packing_shortfall and carton_report are free, unlimited and write nothing, so leave them enabled permanently and re-run them after every packed line. line_pack is the tool that moves the record, and a line packed into a carton that does not exist is refused by name rather than filed somewhere odd.
| You say | Tool |
|---|---|
| Open a packing list against WO-2026-0044 for Harbour Cafe, shipping to 12 Dock Road, Bristol. | packing_list_create |
| Box 1 is 40 by 30 by 25, tare 800 grams: eight shelves at 1250 grams and all twenty-four brackets at 150. | carton_add then line_pack |
| What will DHL charge me for at their 5000 divisor? | carton_report |
On the worked shipment the chargeable weight is 20.000 kg at divisor 5000 and 20.400 kg at 4000, and only the second carton changes basis. A server that hardcoded 5000 would have under-billed that shipment by 400 g and nobody would have found it until the carrier's account was reconciled. The unit suite asserts that no currency symbol reaches the rendered slip, because a packing slip is the one document in this estate that must not carry money.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: packing-list.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"packing-list": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/packing-list/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/packing-listThat writes servers/packing-list/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"packing-list": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-packing-list"]
}
}
}The Customize page shows the server and its tools once it has started.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/packing-list over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"packing-list": {
"url": "https://mcp.zovo.one/mcp/packing-list",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: Three open packing lists, draft and packed, with unlimited cartons, packed lines and declared order lines on every tier. The cap counts shipments in flight rather than shipments ever made, so marking one shipped or cancelling it frees its slot, and deleting a draft is free on every tier. Every text answer, including the packing slip itself, is free. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Packing List pasting the config block above is the supported route.
MCP Packing List in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro
Producing a delivery schedule or a work order document from a chat · Credit notes and purchase orders from chat, against your real invoices