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.
In agent mode the one thing an agent must not do is put money on the slip: the slip carries no prices at all and no currency symbol reaches the render, because the invoice against the same order is a different document. The chargeable weight is max(gross, volumetric) at a divisor you pass, 4000, 5000 or 6000, because the divisor is a tariff term, not a constant.
| 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 .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the user profile mcp.json, opened by the MCP: Open User Configuration command |
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.
VS Code reads its own config, so here it is:
// .vscode/mcp.json (the key is "servers")
{
"servers": {
"packing-list": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/packing-list/dist/index.js"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"packing-list","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:
code --add-mcp '{"name":"packing-list","command":"npx","args":["-y","@theluckystrike/mcp-packing-list"]}'VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.
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.
{
"servers": {
"packing-list": {
"url": "https://mcp.zovo.one/mcp/packing-list",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.
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.
The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.
No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.
In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.
MCP Packing List in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code 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