Developer · Remote MCP server
Labelixa
Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.labelixa/zpl- Version
- 0.4.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- com.labelixa
- Namespace
- Namespace verified by the MCP Registry via the domain labelixa.com · how
- Website
- labelixa.com/mcp
- Repository
- github.com/Labelixa/labelixa-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.labelixa.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- labelixa 0.4.0 · protocol 2025-06-18
- Tools discovered
21 - show names
zpl_preview,zpl_validate,zpl_command_help,barcode_png,language_detect,epl_validate,tspl_validate,cpcl_validate,explain_zpl,convert_zpl_dpi,template_list,template_get,epl_preview,tspl_preview,cpcl_preview,image_to_zpl,barcode_verify,zpl_compatibility,bulk_submit,bulk_status,bulk_list- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | labelixa-mcp | 0.4.1 | stdio |
How to connect Labelixa
Labelixa is a remote MCP server: there is nothing to install. Its endpoint is https://api.labelixa.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: labelixa-mcp version 0.4.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y labelixa-mcp@0.4.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"zpl": {
"command": "npx",
"args": [
"-y",
"labelixa-mcp@0.4.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Kvm PilotHands for your AI agents - write-capable KVM+BMC+SSH MCP server: gated, verified, audited. | Local · stdio |
| Kweenkl MCPPush notifications for AI agents - send instant iPhone notifications from any MCP client. | Remote · HTTPLive check: ✓ handshake |
| KworkAccount-bound, typed and durable stdio MCP gateway for the Kwork freelance marketplace. | Local · stdio |
| LabbyRust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI. | Local · stdio |
| LabTestSuperstoreRead-only U.S. lab-test catalog, collection-site search, and reference-range context. | Remote · HTTPLive check: ✓ handshake |
| LachesisCompiler-precise code property graph for C, Python, and TypeScript, navigable over MCP. | Local · stdio |
| LaguardeSelf-hostable policy control plane for AI coding agents. | Local · stdio |
| LainHigh-performance knowledge graph MCP server for AI coding agents with semantic search. | Local · stdio |