Home · Setup · Claude Desktop

MCP Barcode in Claude Desktop

QR codes and barcodes drawn locally: SEPA payment codes, WiFi, vCard, Code 128, EAN-13. It draws a QR code from text or a URL, a WiFi join code, a vCard, an EPC069-12 SEPA payment code checked against the shared business profile's IBAN, and Code 128, EAN-13, EAN-8 or UPC-A with the check digit computed or verified. No network call of any kind.

A generated SVG comes back as an inline preview in the reply, which is the exact form you are about to paste into a flyer, a proposal or an invoice template already open in another window, and the 4000 px PNG ceiling on Pro covers a print job without this window ever needing a filesystem picker.

What you get in Claude Desktop

You say	Tool
Make a QR code for this URL.	`qr_create`
Put a payment QR code on invoice INV-2026-0007.	`invoice_payment_qr`
Give this SKU a Code 128 barcode.	`barcode_create`

The first Code 128 table transcription was missing one row, silently shifting 67 of 107 values to their neighbour: a clean-looking barcode that scanned as the wrong string. Comparing against an independent encoder caught it; every table is now pinned against that comparison in the test suite.

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 barcode.mcpb from the bundle catalog 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": {
    "barcode": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/barcode/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/barcode

That writes servers/barcode/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": {
    "barcode": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-barcode"]
    }
  }
}

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

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/barcode 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": {
    "barcode": {
      "url": "https://mcp.zovo.one/mcp/barcode",
      "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: 20 codes a calendar month, every symbology and QR kind, SVG output. 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 Barcode 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 Barcode 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

Related guides & tools

Generate barcodes and QR codes from chat with an MCP server · Run a stock count with barcodes and update the catalogue in chat