MCP Server

Labelixa runs a remote MCP (Model Context Protocol) server, so MCP-compatible AI clients can preview, validate and diagnose label code and generate barcodes as first-class tools. Verified with Claude Desktop and Claude Code; any MCP-compatible client can connect.

Available tools

These are the tools the server exposes today — the list below is generated from the live tool registry, not copied by hand:

zpl_preview — Render ZPL label code and return the label as a PNG image.
zpl_validate — Lint ZPL code and return structured diagnostics: unknown commands, missing ^FS, out-of-range parameters, fields outside the label boundary.
zpl_command_help — Explain a single ZPL command: syntax, parameters with types/ranges/options, a fragment example and whether the Labelixa renderer draws it.
barcode_png — Generate a single barcode as a PNG image (Code 128, QR, DataMatrix, EAN-13, UPC-A, PDF417 and more).
language_detect — Detect which printer language raw label code is written in (ZPL, EPL, TSPL or CPCL).
epl_validate — Lint EPL/EPL2 label code; returns positioned findings with severity as JSON.
tspl_validate — Lint TSPL/TSPL2 label code; returns positioned findings with severity as JSON.
cpcl_validate — Lint CPCL label code; returns positioned findings with severity as JSON.
explain_zpl — Full health report for a ZPL label: sectioned findings (syntax, size/DPI, orientation, barcodes, fonts, graphics memory, job behaviour) with an honest score — sections that cannot be assessed say so and are excluded from the score.
convert_zpl_dpi — Rescale ZPL between printer resolutions (203/300/600 DPI): coordinates, fonts, barcode module width and label size are scaled.
zpl_compatibility — Compatibility RISK analysis of ZPL code against a specific printer model (e.g.

Endpoint

Streamable HTTP (JSON-RPC) at https://api.labelixa.com/mcp. GET serves this page; the protocol speaks over POST.

Authentication and quotas

No key is required: anonymous calls share the free, per-IP rate-limited tier. Send your key in the X-API-Key header (or as a Bearer token) to use your plan's daily quota instead. MCP calls pass the same rate and quota gates as the REST API — MCP is not a quota bypass.

Configuration

Add the server to an MCP-compatible client (Claude Desktop format shown). A local stdio alternative is published on npm as labelixa-mcp.

{
  "mcpServers": {
    "labelixa": {
      "type": "http",
      "url": "https://api.labelixa.com/mcp"
    }
  }
}

Security and privacy

Tool calls follow the same stateless path as the REST API: submitted label code is processed in memory and returned, not stored. Details on the security page.