thermal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| preview_htmlA | Render ticket HTML WITHOUT printing. Returns the EXACT 1-bit image that would be printed (after dithering/thresholding) — always preview before print_html. |
| print_htmlA | Render ticket HTML and print it on the thermal printer. Preview with preview_html first. |
| design_guideA | Read this FIRST before designing any thermal ticket. Returns the full design guide: the two paths (markdown vs custom HTML), type-size tiers, the bundled font/icon library, graphics helpers, house style, and layout best practices for 58mm 1-bit thermal paper. Client-agnostic (works in Claude Desktop, which does not load the Claude Code skill). |
| preview_markdownA | Render markdown WITHOUT printing. Returns the EXACT 1-bit image that would be printed — preview before print_markdown. |
| print_markdownA | Render markdown with the built-in ticket style and print it on the thermal printer. Quick path for notes/lists/receipts; use print_html for custom design. |
| printer_statusB | Check printer/transport status and current configuration. |
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 6 tools
Each tool has a distinct purpose: previewing vs printing, HTML vs Markdown, checking status, and reading the design guide. No two tools overlap in function, and the descriptions clarify the exact use case for each.
Most tools follow a clear verb_noun pattern: preview_html, print_html, preview_markdown, print_markdown. Two exceptions (printer_status, design_guide) are noun phrases, but they are still intuitive and don't create confusion.
With 6 tools, the set is well-scoped for thermal printing workflows. Each tool earns its place, covering preview, print, status, and guidance without unnecessary bloat.
The surface covers the full lifecycle: design (design_guide), validate (preview_*), execute (print_*), and monitor (printer_status). No obvious dead ends or missing essential operations for the domain.