Home · Setup · Claude Desktop

MCP Goods Receipt in Claude Desktop

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.

The delivery note is usually already photographed in this window, so reading what arrived, damaged and short straight out of the picture into grn_add and grn_line_add is one sentence, and the month-end question that matters, what is still wrong across every receipt, is the next one. Nothing leaves the machine: the server makes no network call on any tool, so the whole GRN ledger stays on the warehouse laptop it was typed on.

What you get in Claude Desktop

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.

Install it in Claude Desktop

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

Scope	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

One click, with no JSON. Download goods-receipt.mcpb from the latest release 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": {
    "goods-receipt": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/goods-receipt/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/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:

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

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 latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

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.

{
  "mcpServers": {
    "goods-receipt": {
      "url": "https://mcp.zovo.one/mcp/goods-receipt",
      "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: 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.

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 Goods Receipt 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.

MCP Goods Receipt 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