Barcode Labels Docs

Connect Claude (MCP)

Design, print and save labels from Claude and other AI agents through the hosted MCP server.

Barcode Labels hosts a remote Model Context Protocol server so AI agents can design labels, generate barcodes and print to label stock inside a conversation.

Server URL: https://barcodelabels.io/api/mcp (Streamable HTTP, no trailing slash)

Add it to Claude

In Claude, open Settings → Connectors and choose Add custom connector.

Paste https://barcodelabels.io/api/mcp as the server URL. Leave the OAuth client fields empty.

Click Connect. You will be sent to our sign-in page (hosted at auth.factoryapps.io, the identity service for TriPeak Technology products) to create or sign in to your account, then approve the connection.

Claude Code works too:

claude mcp add --transport http barcode-labels https://barcodelabels.io/api/mcp

What you can ask

Describe the label the way you would to a colleague:

I need a 4x2 label for bin A1-03: part number M8-HEX-30 in the top left, quantity 250 in the top right, and a Code 128 of the part number along the bottom.

Claude lays it out with design_label, checks the preview, and gives you a print-ready PDF plus a link that opens the design in the Designer for fine-tuning.

Save that as "Bin label" with the part number and quantity as fields.

save_template stores it in your account (or an organization you can edit) with {Part} and {Qty} fields, ready for Basic mode, CSV runs or the Designer.

Print 20 of my Bin label for part M6-HEX-20, quantity 100.

list_templates finds it and render_template prints it with those values.

Tools

ToolWhat it does
design_labelLays out text, barcodes, lines and boxes by position (top-left, bottom-center, ...) on any label size. Preview, PDF and Designer links.
save_templateSaves a design as a new template in your account or an organization. Never changes or deletes existing templates.
list_templatesLists your saved templates and your organizations' shared templates, with their fields.
render_templatePrints a saved template with field values filled in. Preview plus a private PDF link valid for 24 hours.
generate_barcodeRenders a single barcode as a PNG, plus PNG/SVG/PDF URLs on the REST API.
generate_labelRenders one barcode on a label-stock sized page (4x6, 2x1, 100x150 mm, ...) with a print-ready PDF link.
validate_barcode_dataChecks whether text is encodable in a symbology (check digits, allowed characters) without rendering.
list_barcode_typesLists all supported symbologies with their data requirements.
list_label_sizesLists the accepted label sizes.
get_api_referenceReturns a compact reference for the free REST API, for agents writing integration code.

save_template is the only tool that writes, and it only adds. Every tool carries read-only/destructive annotations, so Claude can run the read-only ones without asking and confirms before saving.

Authentication and access

The MCP server uses OAuth 2.1 with a Barcode Labels account. Sign-in is handled by our identity provider; Claude never sees your password. Tokens are bound to this server only.

Through Claude you can do what you can do on barcodelabels.io: use your own templates, view your organizations' templates, and save to organizations where your role allows editing.

Design and image results include the equivalent REST API URLs. These links are signed for your account: anyone with the link can open them without an API key for 30 days, and every label they print counts toward your account's allowance (500 free labels/day, more with a pack or plan), so share them like any other link. After 30 days a link falls back to the keyless limits. Print links for saved templates are private to your account, expire after 24 hours, and also count toward your allowance.

For other MCP clients

The server follows the MCP authorization specification: an unauthenticated request receives 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/api/mcp, which names the authorization server. Clients that support Client ID Metadata Documents connect without pre-registration. PKCE (S256) is required.

Privacy

Designs you make in a conversation are rendered on request and not stored unless you save them; their links carry the design in the URL itself. Saved templates are stored in your account like templates saved from the app. Account data (email and display name) is held by our identity provider and used solely to authenticate you.

On this page