labelixa-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LABELIXA_API_KEY | No | Optional `lbx_` API key. Without it the anonymous quota applies. Get a key at https://labelixa.com. | |
| LABELIXA_BASE_URL | No | Optional base URL for the Labelixa API. Defaults to https://api.labelixa.com. |
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 |
|---|---|
| zpl_previewA | Render ZPL label code to a PNG image via the Labelixa API. This is a SERVER-SIDE render for inspection — it is not a guarantee of how a specific physical printer will output the label. |
| zpl_validateA | Lint/validate ZPL and return the structured diagnostics report (unknown commands, parameter range errors, layout overflow, etc.) as JSON. Pass the real label size — checks depend on it. |
| barcode_generateA | Generate a standalone barcode (SVG text or PNG image). Supported types include code128, code39, ean13, upca, upce, itf14, msi, qrcode, datamatrix, pdf417. |
| language_detectA | Detect which printer language raw label code is written in (ZPL, EPL, TSPL or CPCL). Heuristic: returns the language plus a confidence TIER (high/medium/low) and signal codes — not a probability. |
| epl_validateA | Lint/validate EPL/EPL2 label code and return the structured diagnostics report (findings with positions and severity) as JSON. |
| tspl_validateA | Lint/validate TSPL/TSPL2 label code and return the structured diagnostics report (findings with positions and severity) as JSON. |
| cpcl_validateB | Lint/validate CPCL label code and return the structured diagnostics report (findings with positions and severity) as JSON. |
| zpl_compatibilityA | Compatibility RISK analysis of ZPL code against a specific printer model, given as manufacturer/model (e.g. 'zebra/zd421'). NOT an emulator and never says 'it works': reports the model's language posture with evidence level, size-rule findings and the scope of our preview. |
| zpl_command_helpA | Look up one ZPL command in the maintained catalog: name, syntax, parameters (types, ranges, defaults) and whether the preview engine actually renders it — printer-side commands are honestly marked as not rendered. |
| convert_zpl_dpiA | Rescale ZPL coordinates between printer resolutions (203/300/600 dpi). Embedded ^GF/~DG bitmap data is NOT rescaled — when present, a Warnings block precedes the output instead of silently passing. |
| explain_zplA | Full sectioned health report for a ZPL label (syntax, size/DPI, orientation, barcodes, fonts, memory) with an honest score: only assessable sections count, the rest say 'not assessed'. Pass the real label size — findings depend on it. |
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 11 tools
The four language validators are cleanly separated by language prefix, and preview, barcode generation, DPI conversion, and language detection have distinct purposes. Only zpl_validate and explain_zpl overlap meaningfully as both analyze ZPL and can report issues, though explain_zpl's sectioned health-report framing helps separate them.
The validators follow a clear <language>_validate pattern and ZPL tools generally share a zpl_ prefix. However, barcode_generate and language_detect use object_verb order, while convert_zpl_dpi and explain_zpl lead with verbs, creating mixed but readable conventions.
Eleven tools is well within the appropriate range for a label-printing utility server and each area of functionality has a dedicated tool without obvious redundancy. The count feels earned: validation for four languages plus ZPL-specific rendering, compatibility, conversion, help, and diagnostics.
The server covers detection, validation for all four major label languages, barcode generation, and a solid ZPL workflow from command lookup through rendering, conversion, compatibility, and health reporting. The main gap is that preview, conversion, and command help exist only for ZPL, not for TSPL/EPL/CPCL.