Home · Guides

A stock count you talk through, barcode by barcode

A physical count produces a list of codes and quantities, and the useful output is a tidy catalogue whose levels reflect what you actually have. MCP Barcode resolves the codes and MCP Catalogue holds the items, so the count updates stock rather than creating a second record you later reconcile.

Resolve the code, read the item

Hand it the codes you scanned and it looks the item up in the catalogue, so a list of numbers becomes item names, units and current levels. "These 40 codes are the after-hours count; report the ones that differ from the book" surfaces the discrepancies while they are cheap to fix, instead of burying them in a reconciled spreadsheet two weeks later.

The count is the update

Adjusted quantities write back to the catalogue entries, so the stock level moving is the same action as recording the count. There is no intermediate file to lose. When the count confirms the registers, you are done; when it finds a hole, the same chat starts the replacement order.

One click, with no JSON. Download barcode.mcpb from the latest release and open it in Claude Desktop. It runs on the Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.

Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready line:

claude mcp add --transport http barcode https://mcp.zovo.one/mcp/barcode/t/<token>

Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/barcode

claude mcp add --scope user barcode -- node /absolute/path/to/mcp-servers/servers/barcode/dist/index.js

Claude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in claude_desktop_config.json or the client's own MCP config file:

{
  "mcpServers": {
    "barcode": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/barcode/dist/index.js"]
    }
  }
}

The npm packages are not published yet, so the npx form below returns a 404 today. It is kept because it is what that config becomes the day the publish lands, with nothing else changed; installing these servers when npx does not work yet has the whole picture.

claude mcp add barcode -- npx -y @theluckystrike/mcp-barcode

Questions

Do I need a hardware scanner?

No. Pass in the codes however you captured them, whether a scanner, a label photo import or a typed list, and the server resolves them against the catalogue.

What happens to items not in the catalogue?

They are reported as unknown so you can add them or tell the server and it notes them separately; the count never silently merges an unknown code into an existing item.

Does the count update stock levels?

Yes. An adjusted quantity writes back to the catalogue entry, so the recorded count and the stock figure are the same number, not two lists that need reconciling.

All MCP servers and prices · All guides · Buy the bundle $39