Goods receipt notes against purchase orders: what arrived, what was damaged, what never came. You raise a purchase order with whole-unit lines, then receive it as a goods-receipt note (GRN): one cell per PO line for units received and units damaged. Received is checked against the PO line's tolerance before the note opens, more lines and more units can be added as batches arrive, and grn_close freezes the note. grn_discrepancy lists every line not as ordered (damaged, declared shortage, or received under tolerance), the status report counts notes open, closed and discrepant, and the CSV export hands the whole ledger to the accounts side. GRN ids are sequential and never reissued; closing is the record, not deletion.
In agent mode the discrepancy list must come from the server: grn_discrepancy compares received against ordered with the tolerance on each line, so an agent reconciling by hand is composing an estimate the server already gives exactly.
| You say | Tool |
|---|---|
| Raise a PO for 40 cases of glassware and 12 crates of bottle openers. | po_add |
| The glassware truck came: 38 cases fine, 2 broken. Open a GRN. | grn_add |
| What is still wrong across everything we received this month? | grn_discrepancy then grn_status_report |
The unit suite is 18 tests, 18 passing, 0 failing (node --test, node v22), covering tolerance checks on received, damage and shortage per line, and the close discipline. The contract suite asserts the snapshot rule on the raw store bytes, not only through the API.
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: goods-receipt.mcpb
from the latest release 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": {
"goods-receipt": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/goods-receipt/dist/index.js"]
}
}
}
Or from a terminal:
code --add-mcp '{"name":"goods-receipt","command":"node","args":["/absolute/path/to/mcp-servers/servers/goods-receipt/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/goods-receipt
That writes servers/goods-receipt/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":"goods-receipt","command":"npx","args":["-y","@theluckystrike/mcp-goods-receipt"]}'
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 latest release, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/goods-receipt 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": {
"goods-receipt": {
"url": "https://mcp.zovo.one/mcp/goods-receipt",
"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: Purchase orders, receipt notes, line additions, the discrepancy list and the status report are all free and unlimited; the estate pattern caps nothing a warehouse needs day to day. Every read is free on every tier. 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 Goods Receipt in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro