{
  "markdown": "# 3DPACK.ING MCP server\n\nContainer and truck load planning for AI assistants. Describe a shipment in plain\nEnglish; get back the containers it fits in, how full each one is, what did not fit,\nand a link to an interactive 3D load plan.\n\nBacked by the [3DPACK.ING](https://3dpack.ing) solver — the same one behind the web\nplanner. Asked \"will 500 cartons fit in a 40-foot\", an assistant without this will do\narithmetic on volumes, which ignores stacking rules, orientation and weight limits and\noverstates what fits by a wide margin on real cargo.\n\n## Install\n\n### Hosted (no install)\n\nThe server runs at `https://3dpack.ing/mcp` over streamable HTTP. Nothing to install,\nand it answers on the first call without an account.\n\nClaude Code:\n\n```bash\nclaude mcp add --transport http 3dpacking https://3dpack.ing/mcp\n```\n\nAny client that takes a URL — add `https://3dpack.ing/mcp`. To use your own key\ninstead of the shared demo account, pass it in the query string:\n\n```\nhttps://3dpack.ing/mcp?apiKey=your-key&username=your-username\n```\n\nor send `X-3dpacking-Api-Key` and `X-3dpacking-Username` headers, if you would rather\nnot put a key in a URL. Both are needed together — the API rejects a key without the\naccount it belongs to.\n\n### Local (npm)\n\nClaude Desktop — add to `claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"3dpacking\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@3dpacking/mcp-server\"]\n    }\n  }\n}\n```\n\nClaude Code:\n\n```bash\nclaude mcp add 3dpacking -- npx -y @3dpacking/mcp-server\n```\n\nIt works immediately, with no account — the first call runs against a shared demo\naccount on the free plan. For your own limits, sign up at\n<https://3dpack.ing/login> and add:\n\n```json\n{\n  \"mcpServers\": {\n    \"3dpacking\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@3dpacking/mcp-server\"],\n      \"env\": {\n        \"THREEDPACKING_API_KEY\": \"your-key\",\n        \"THREEDPACKING_USERNAME\": \"your-username\"\n      }\n    }\n  }\n}\n```\n\nBoth must be set together — the API rejects a key without a username.\n\n## The tool\n\n**`pack_shipment`** — one required argument, `prompt`, describing the cargo in plain\nEnglish, and two optional settings: a `speed` of `fast`, `normal` or `thorough`, and a\n`stability` of 75 to 100.\n\n`stability` is how much of a box must rest on what is underneath it, as a percentage of\nits own footprint. Omit it for 75, the standard rule, which lets a quarter of a box\noverhang and packs the most. Raise it for cargo that must not lean — drums, glass,\nanything top-heavy — and use 100 when every stacked box has to sit fully supported. It\nis the one constraint the prompt cannot carry, because it governs how the solver stacks\nrather than what is being shipped, and a higher value fits fewer items.\n\nThings it understands:\n\n```\nPack 50 boxes of 60x40x30 cm into a 20ft container\nLoad 100 fragile items 80x60x40cm, max stack 3, into a 40ft high cube\nShip mixed pallets: 10x euro pallets, 15x US pallets, best container mix\nShip 24 pcs 200.3x120.2x100.2 cm (non-tiltable), optimal mix of 40ft and 20ft\n```\n\nWhat comes back:\n\n```\nEverything fits: 1 container.\n\nContainer 1 (589.3 x 235 x 239 cm internal)\n  items: 50\n  of which: 50x Boxes\n  used: volume 10.9%\n  5 empty gaps left\n\nInteractive 3D load plan: https://3dpack.ing/app?g=6c4b9488-...\n```\n\n## Notes on the shaping\n\nThe API returns the geometry of every unfilled cuboid in every container, with\ncoordinates. That is what the 3D viewer needs and it is most of the payload on a real\nshipment. Spending a model's context on the coordinates of empty space, when the link\nopens a picture of exactly that, is a poor trade — so the summary keeps the *count* of\ngaps and drops the geometry. On a small pack that is 791 bytes down to 341; on a large\none it is the difference between a usable answer and a flooded context.\n\nA plan limit is not reported as an error. The API returns HTTP 500 for\n`NotSubscribed`, the same status it uses for a solver crash; left alone, an assistant\nreads that as \"the service is broken\" and tells the user to try again later, when what\nactually happened is that they asked for a Pro feature. This server sorts the two\napart and relays the offer.\n\nAnything that answers with non-JSON — a proxy, a VPN, a corporate egress allowlist —\nis reported as a network problem naming what actually replied, rather than as a\npacking failure. Only one of those is something the user can fix.\n\n## Environment\n\n| Variable | Purpose |\n|---|---|\n| `THREEDPACKING_API_KEY` | Your API key. Falls back to the shared demo account. |\n| `THREEDPACKING_USERNAME` | The account the key belongs to. Required with the key. |\n| `THREEDPACKING_ENDPOINT` | Override the endpoint — staging, self-hosted, or a stub. |\n\n## Development\n\n```bash\nnpm install\nnpm run smoke     # calls the live solver with demo credentials and checks the shape\n```\n\n`smoke.js` is deliberately not mocked for the live checks. The thing that will break\nthis package is 3dpack.ing changing the shape of its answer, and no amount of mocking\ncatches that. Run it before publishing. To exercise the success path without spending\na calculation, point `THREEDPACKING_ENDPOINT` at a stub.\n\n## Licence\n\nMIT.\n",
  "bytes": 5156,
  "sha": "fc445f6003144edf8f18bfb2cca6dd0a4b80522ce586cad411cfe7f96a1558e3",
  "repo_slug": "onurgumus/3dpacking-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ing_3dpack_bin_packing_05a5f50b/readme"
}