Printix MCP Server
Related Servers
Alternatives to Printix MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to submit PDFs or JSON-rendered templates to local printers, check printer status, and manage print jobs through MCP tools.21 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to drive cloud printers: listing available printers, sending PDFs, ZPL labels and ESC/POS receipts, tracking print jobs through to completion, and managing webhooks. It connects an MCP client to the InkRelay printing API so printing happens from natural language requests.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to print HTML, web pages, PDFs, and images to local printers by bridging to an existing client over WebSocket, including previews, printer discovery, batch jobs, and customizable PDF/print settings.160MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to print documents directly on your own printer over a private network, without cloud services or open ports. Supports printing text, URLs, and files with per-person access keys, usage limits, and detailed job control.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to monitor and control Prusa 3D printers over PrusaLink or Prusa Connect, including status and camera checks, file upload and print control, G-code execution, queue and history access, and responding to printer dialogs.1MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to manage 3D printing inventory, filament spools, printers, projects, and print trackers through a self-hosted Print Vault instance.40AGPL 3.0
TDQS
Scored across 11 tools
Every tool targets a distinct resource/action pair: each of the five core resources has one list operation and one get-by-ID operation, with no overlapping verbs. The only singleton, get_tenant, is clearly unique.
All tool names use the same printix_ prefix with a consistent verb_noun pattern: printix_list_* for collection queries and printix_get_* for single-resource lookups. There is no mixing of styles or vague verb usage.
11 tools is a well-scoped count for a Printix query surface: five resources are each covered by a list/get pair, plus the tenant lookup. No tool is redundant or unnecessary.
The read-only resource coverage is broad, but the server has no create/update/delete or print-job/lifecycle operations, so any management workflow beyond listing and fetching dead-ends. This is a significant gap for a Printix administration context.