Home · Setup · Claude Code

MCP Packing List in Claude Code

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.

`claude mcp add packing-list` at user scope is the level that matches both the meter and the data: three open lists is a warehouse door's allowance rather than a repository's, and the store is one directory per machine anyway. carton_report answers the chargeable-weight question from the terminal without a carrier account open.

What you get in Claude Code

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.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

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. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user packing-list -- node /absolute/path/to/mcp-servers/servers/packing-list/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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-list

That 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:

claude mcp add packing-list -- npx -y @theluckystrike/mcp-packing-list

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

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.

claude mcp add --transport http packing-list https://mcp.zovo.one/mcp/packing-list \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

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.

Questions

Which scope should I use for MCP Packing List?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Packing List without installing anything?

Yes: claude mcp add --transport http packing-list https://mcp.zovo.one/mcp/packing-list --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Packing List in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro

Related guides & tools

Producing a delivery schedule or a work order document from a chat · Credit notes and purchase orders from chat, against your real invoices