A
licenseB
qualityF
maintenanceEnables LLMs to interact with GitHub issues by providing details as tasks, allowing for seamless integration and task management through GitHub's platform.
1
30
14
MIT
MCP Label Printer
by calumjs
Prints labels with QR codes for GitHub issues and pull requests, including issue numbers, titles, and URLs to Brother QL-810W label printer.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Label Printerprint label for PR #87 "Update README with new API docs" with URL https://github.com/org/repo/pull/87"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Label Printer
An MCP server for printing labels with QR codes to Brother QL-810W printer via P-touch Editor Lite.
Prerequisites
Python 3.10+ - Download
Brother QL-810W printer connected via USB
Editor Lite mode enabled on printer (green LED on)
Related MCP server: GitHub PR Review Server
Installation
Clone the repository:
git clone https://github.com/calumjs/MCP.Printer.git cd MCP.PrinterInstall the package:
pip install -e .This installs all dependencies (Pillow, qrcode, brother_ql, mcp).
Verify installation:
python -c "from mcp_label_printer.printer import print_label; print('OK')"
Printer Setup
Connect Brother QL-810W via USB
Press the Editor Lite button until the green LED turns ON
The printer should appear as a USB drive (usually
D:\)Verify
D:\PTLITE.PRNexists
MCP Configuration
Add to your MCP config file:
For Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"label-printer": {
"command": "mcp-label-printer"
}
}
}Alternative (if command not found):
{
"mcpServers": {
"label-printer": {
"command": "python",
"args": ["-m", "mcp_label_printer.server"]
}
}
}Restart your IDE after adding the config.
Usage
The server exposes one tool:
print_label
Print a label with QR code and text.
Parameter | Required | Description |
| Yes | URL to encode in QR code |
| Yes | Issue/PR number (e.g., "#1234") |
| Yes | Issue/PR title |
| No | Brief description |
Example prompt:
Print a label for issue #42 "Fix login bug" with URL https://github.com/org/repo/issues/42
How It Works
Generates a QR code from the URL
Creates a label image with QR code + text
Converts to Brother QL raster format
Writes to
D:\PTLITE.PRNwith proper padding (112,640 bytes)Printer automatically prints when file is written
Troubleshooting
Nothing prints:
Ensure Editor Lite LED is ON (green)
Check
D:\drive exists and containsPTLITE.PRNTry printing from P-touch Editor Lite app to verify printer works
Command not found:
Ensure Python Scripts folder is in PATH
Use the alternative config with
python -m mcp_label_printer.server
Wrong label size:
This is configured for 62mm continuous labels (DK-22205)
Available Tools
1 toolprint_labelB
Print a label with QR code and text to Brother QL-810W printer. The QR code links to the provided URL, and text shows issue details.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to encode in QR code (e.g., issue/PR link) | |
| issue_number | Yes | Issue/PR number (e.g., '#1234') | |
| title | Yes | Issue/PR title | |
| description | No | Brief description (optional) |
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action ('Print') and output format (label with QR code and text), but fails to disclose critical traits such as whether this requires printer connectivity, specific permissions, error handling, or side effects like paper consumption. For a hardware-interaction tool, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that efficiently conveys the tool's purpose and key details without unnecessary words. It is front-loaded with the main action and resource, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (hardware interaction with 4 parameters) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose and parameter mapping but lacks behavioral context, error handling, or output details. For a tool that interacts with physical devices, more information would be beneficial to ensure reliable use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds minimal meaning beyond the input schema, which has 100% coverage with clear descriptions for all parameters. It mentions that the QR code links to the URL and text shows issue details, loosely mapping to the parameters but not providing additional syntax or usage details. Given the high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Print a label'), the target resource ('to Brother QL-810W printer'), and the content ('with QR code and text'). It specifies that the QR code links to a URL and text shows issue details, making the purpose specific and actionable. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It implies usage for printing labels with issue details and QR codes but lacks explicit context or recommendations for specific scenarios. This minimal guidance limits its effectiveness for an AI agent in decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
B3.2/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
Naming Consistency5/5
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'print_label' follows a clear verb_noun pattern.
Tool Count2/5
One tool is too few for a server named 'MCP Label Printer', which suggests a broader scope for label printing operations. A single tool limits functionality and feels thin for the apparent domain.
Completeness2/5
The server lacks obvious operations for a label printing domain, such as listing printers, configuring settings, or managing label templates. The single tool provides basic printing but leaves significant gaps in coverage.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Preview ZPL labels as PNG, validate ZPL with structured diagnostics, generate barcodes.
Scan QR codes and go! No more troublesome autos or APIs! Send text messages, images, links, locati…
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables automated GitHub Pull Request reviews using local Ollama, Cursor CLI, or Gemini CLI as AI providers. Supports customizable review prompts, comprehensive PR analysis, and optional auto-posting of reviews to GitHub.135MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of GitHub projects and issues using GitHub's GraphQL API. Supports creating/updating issues with images, managing labels and assignees, organizing ProjectsV2 boards, and updating project item statuses.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI-powered GitHub automation by connecting Claude AI with GitHub APIs for managing issues and pull requests.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/calumjs/MCP.Printer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server