Home · Setup · Cline

MCP Barcode in Cline

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.

code_list and license_status are reads and safe to auto-approve; leave the eight drawing tools and license_activate behind a click, since each one writes a file to disk or spends one of this month's 20 free codes.

What you get in Cline

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 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`

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

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

The npm publish of @theluckystrike/mcp-barcode is pending; until then use the .mcpb bundle or a clone and build from the latest release.

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.

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

{
  "mcpServers": {
    "barcode": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/barcode",
      "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: 20 codes a calendar month, every symbology and QR kind, SVG output. 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 Barcode'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 Barcode in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs