Home · Setup · Cursor

MCP Goods Receipt in Cursor

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 and grn_status_report are free, unlimited and write nothing, so leave them enabled permanently and read the ledger as often as you like. grn_add and grn_line_add are the deliberate ones: received units are checked against the PO line's tolerance before the note opens, and the server asks which line rather than guessing.

What you get in Cursor

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 Cursor

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

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

The config block:

{
  "mcpServers": {
    "goods-receipt": {
      "type": "stdio",
      "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:

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

The Customize page shows the server and its tools once it has started.

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

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Goods Receipt pasting the config block above is the supported route.

Related

MCP Goods Receipt in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro