mcp-barcode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTHORIZATION_BEARER_TOKEN | No | Token for the hosted endpoint (https://mcp.zovo.one/mcp/barcode), sent as `Authorization: Bearer <token>` or, if your client cannot set headers, in the path instead (https://mcp.zovo.one/mcp/barcode/t/<token>). A free anonymous token is issued at https://mcp.zovo.one/mcp/connect; the bare URL with no token answers 401 on tools/call, so the token is not optional when using the hosted server. Not needed when running from source or via the .mcpb bundle, where there is no network call and no API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| license_statusA | Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key. |
| license_activateA | Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back. |
| qr_createA | Call this tool to turn text or a URL into a QR code: SVG inline, or a PNG at a pixel size to out_path (Pro). Returns version, module grid and payload size. Free: 20 codes a month on this server. |
| qr_wifiA | Call this tool to make a QR code that joins a WiFi network when scanned: ssid, password and auth type, written to out_path or returned as SVG. Free: 20 codes a month. qr_create takes plain text or a URL. |
| qr_vcardB | Call this tool to make a QR code that adds a contact when scanned (vCard 3.0). For your own card pass nothing: name, phone, email and address default to the shared business profile, never asked for. |
| qr_payment_sepaA | Call this tool for an EPC069-12 payment QR a euro banking app can scan. Amount and reference are enough: the beneficiary IBAN and name default to the shared business profile, never asked for. |
| invoice_payment_qrA | Call this tool for a SEPA payment QR from just an amount and reference: IBAN and name are read from the shared business profile, never asked for; pass invoice_id instead to take the amount from an invoice. |
| barcode_createA | Call this tool to draw a linear barcode (code128, ean13, ean8, upca) as SVG, or PNG to out_path. A short EAN or UPC gets its check digit computed; a wrong one is refused, never redrawn. qr_create makes QR codes. |
| barcode_batchA | Call this tool to draw many barcodes or QR codes at once from a list of rows, each with its own value and file name, into out_dir. Pro; the free tier does one code per call. |
| code_listA | List the codes this server generated, newest first, with what each carried and where it went, plus how much of the free 20 a month is used. Filter by kind. It reads the register, not the files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools are clearly separated by payload type (qr_create for text/URL, qr_wifi, qr_vcard, barcode_create, barcode_batch, code_list, and the two license tools). However, invoice_payment_qr and qr_payment_sepa both produce a SEPA payment QR from an amount and reference using the shared business profile's IBAN, so an agent can easily pick the wrong one. The descriptions hint at a difference (invoice_id lookup vs. raw amount), but the boundary is thin and the names do not reinforce it.
The set follows a readable <domain>_<action> convention: qr_*, barcode_*, code_list, license_*. The only real deviations are invoice_payment_qr, which inverts the order used by its near-twin qr_payment_sepa, and the noun_noun license_status alongside noun_verb license_activate. These are minor and still parseable.
Ten tools is a well-scoped set for a QR/barcode generator, with each family (QR types, barcode, batch, history, licensing) earning its place. The only questionable inclusions are two license tools and two near-duplicate payment tools, which nudge it just over the minimum needed.
The core lifecycle is covered: generate single codes (text, WiFi, vCard, SEPA), generate barcodes and batches, list history, and manage licensing. Gaps are minor rather than blocking: no structured QR types beyond WiFi/vCard/payment (e.g. email, SMS, geo), no decode/read-back of an existing code, and no way to delete or prune generated files or history entries.