mcp-barcode

MCP server for QR code and barcode generation: generates barcodes and QR codes. QR codes and barcodes drawn on your machine, with no upload and no network call.

Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.

Product page: https://mcp.zovo.one/s/barcode — what it does, the tools it exposes, and a live token endpoint.

Install

Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/barcode over streamable-http and send the token as Authorization: Bearer <token>.

If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/barcode/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.

Claude Desktop, one click. Download barcode.mcpb from the latest release and double-click it.

From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.

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

Then point your client at the built entry point:

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

@theluckystrike/mcp-barcode is not published on npm yet, so an npx -y @theluckystrike/mcp-barcode command will fail. The three paths above are the working ones and each is exercised by CI.

Read-only mirror of mcp-servers/servers/barcode. See MIRROR.md.

Make a QR code or a barcode in the conversation you are already in. Paste a URL and get a QR code you can put on a flyer. Give a client's invoice an EPC payment code their banking app scans and fills in for them. Print an EAN-13 for a product, a Code 128 for a shelf label, a WiFi code for the office wall, a vCard for a conference badge. Everything is drawn on your machine: no upload, no account, no API key, and no network call of any kind.

In the official MCP Registry (io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13).

Listed on the AI Product Index — live remote endpoint at mcp.zovo.one/s/barcode, free tier, no signup.

npm publish for @theluckystrike/mcp-barcode is pending, so npx -y @theluckystrike/mcp-barcode returns 404 today. Until then, the .mcpb one-click bundle or a clone+build is the working path.

Related MCP server: QRzap MCP Server

Install

Claude Desktop, ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

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

Claude Code:

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

Cursor, .cursor/mcp.json:

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

Tools

Free vs Pro

Get Pro: https://mcp.zovo.one/buy/barcode - $19 one time, or $39 for every server in the suite, lifetime. Keys verify offline; nothing is sent anywhere.

A wrong check digit is refused, not redrawn

Give barcode_create twelve digits and the thirteenth is computed for you. Give it thirteen and the thirteenth is checked:

Error: EAN-13 check digit is wrong: "5901234123450" ends in 0, but the first 12 digits give 7.
Pass 5901234123457, or pass the first 12 digits and the check digit is computed. Nothing was written.

The alternative, silently redrawing the code the caller asked for, prints a label that scans as a different product, and nobody finds out until the till. The same rule applies to the IBAN in a payment code: it is validated with ISO 7064 mod 97 before anything is drawn, so a transposed pair of digits is caught here rather than by a payment that goes nowhere.

Measured: error correction M is free on a SEPA payment code, Q and H are not

A typical EPC payment record (IBAN, beneficiary, EUR 120.50, an invoice number) is 73 bytes. QR codes come in fixed capacity steps, so raising the error correction level does not raise the code size smoothly:

L and M land in the same version 4 symbol: at this payload size the extra recovery data still fits in the same box, so choosing L over M buys nothing and gives up half the damage tolerance. That is why M is the default here. Q and H are worth asking for only when the code will be printed small, on something that creases, or behind a logo. On a 300 px PNG the same step costs bytes too: 2,419 at M against 3,462 at H.

Measured: SVG is flat, PNG grows 14x, and they cross at about 200 px

The same payment code written both ways, at five sizes:

An SVG carries the module grid, not the pixels, so its size barely moves: the two extra bytes at 1024 px are the width attribute getting longer. Below roughly 200 px a PNG is smaller; above it the PNG grows without limit and the SVG does not, and the SVG is the one that stays sharp when a printer scales it up. That is the reason the free tier is the SVG tier rather than a small-PNG tier: for the thing most people do with a code, put it in a document and print it, SVG is the better file, not the consolation prize.

Privacy

Everything stays on your machine. There is no network code in this server at all: no fetch, no HTTP client, no telemetry. Codes are written where you say, and a small register of what was generated lives under ~/.local/share/mcp-servers/barcode/ (or $XDG_DATA_HOME). License keys verify offline with a public key.

Built by theluckystrike. Support: support@zovo.one

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP — no install:

• Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-barcode