Home · Guides

Packing lists and delivery notes straight from the sale

An order is line items; a packing list is those items with a date, a number and the quantities that physically left. MCP Packing List builds the document from the order you describe in chat, so the dispatch paperwork and the sale agreement cannot drift apart.

Numbered, dated, itemised

"Make a packing list for order PO-104 with two enclosures" produces the itemised list with its own number and date, so the goods you sent are the goods on paper. Because the list is generated rather than typed, a correction to a quantity recalculates rather than leaving a stale row behind.

The invoice that follows

Dispatch paperwork is the front half of fulfilment. When the goods go out, the same line items become the MCP Invoice for the customer, so quantities and totals carry over instead of being re-entered. The pair keeps packing, delivery and billing describing the same sale.

One click, with no JSON. Download packing-list.mcpb from the latest release and open it in Claude Desktop. It runs on the Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.

Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready line:

claude mcp add --transport http packing-list https://mcp.zovo.one/mcp/packing-list/t/<token>

Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:

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

claude mcp add --scope user packing-list -- node /absolute/path/to/mcp-servers/servers/packing-list/dist/index.js

Claude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in claude_desktop_config.json or the client's own MCP config file:

{
  "mcpServers": {
    "packing-list": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/packing-list/dist/index.js"]
    }
  }
}

The npm packages are not published yet, so the npx form below returns a 404 today. It is kept because it is what that config becomes the day the publish lands, with nothing else changed; installing these servers when npx does not work yet has the whole picture.

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

Questions

Is a packing list the same as an invoice?

No. A packing list travels with the goods and lists quantities shipped. The invoice comes after and adds pricing and totals. The same server-side line items feed both, which is what keeps them consistent.

Can I reuse one order for several dispatches?

Yes. Describe the line items again with the new quantities and the list is regenerated with a fresh number and date, rather than a copy that had to be hand-edited.

All MCP servers and prices · All guides · Buy the bundle $39