Home · Setup · Claude Desktop

MCP Packing List in Claude Desktop

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.

The order confirmation the slip is packed against is usually already in this window, so declaring the order lines out of it and into packing_list_create is one sentence, and the question that follows, what is still to pack, is the next one. Nothing leaves the machine: there is no network call in the server on any tool.

What you get in Claude Desktop

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 Desktop

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

One click, with no JSON. Download packing-list.mcpb from the bundle catalog and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

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

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

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:

{
  "mcpServers": {
    "packing-list": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-packing-list"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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.

{
  "mcpServers": {
    "packing-list": {
      "url": "https://mcp.zovo.one/mcp/packing-list",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

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

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Packing List does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

Related

MCP Packing List in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop 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