Skip to main content
Glama
WYRE-AI

Printix MCP Server

by WYRE-AI

Related Servers

Alternatives to Printix MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to submit PDFs or JSON-rendered templates to local printers, check printer status, and manage print jobs through MCP tools.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      16
      0
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to manage 3D printing inventory, filament spools, printers, projects, and print trackers through a self-hosted Print Vault instance.
      40
      AGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues