Home · Setup · Cline

MCP Goods Receipt in Cline

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.

grn_list, grn_get, grn_discrepancy, grn_status_report and grn_export_csv are reads or file exports and safe to auto-approve once the path is yours. Keep grn_add, grn_line_add and grn_close behind a click: closing freezes the note, and a GRN number is never reissued, so a gap in the series is the record that a note was closed against the wrong truck. Nothing here ever writes into another server's store.

What you get in Cline

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 Cline

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

Scope	Path
Cline CLI	`~/.cline/mcp.json`
The editor extension	`opened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension`

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. Cline reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "goods-receipt": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/goods-receipt/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

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"]
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

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.

Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:

{
  "mcpServers": {
    "goods-receipt": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/goods-receipt",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

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 does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.

Should I auto-approve MCP Goods Receipt's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

MCP Goods Receipt in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro