Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Related Servers

Alternatives to ipp-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to list installed Windows printers and print PDF files with options for copies, page ranges, monochrome, and duplex.
      408 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to submit PDFs or JSON-rendered templates to local printers, check printer status, and manage print jobs through MCP tools.
      26 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A cross-platform MCP server that enables AI assistants to manage printers, query printer status, and print files on Windows, macOS, and Linux.
      14
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to submit, slice, and start 3D prints with configurable gates, preview approval, and monitoring, via a self-hosted print daemon.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive a Windows print workstation by opening photo folders, setting formats, cropping and color-correcting images, planning sheets, running preflight checks, and printing photos or documents under configurable permission limits.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables printing labels whose layout adapts to the roll reported by a CUPS/IPP label printer, as well as PDF, Markdown, and HTML documents, with preview, copies, duplex, page ranges, and print-job management.
      7
      MIT

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool maps to a distinct resource+action across three clear groups (uploaded files, print jobs, printers), and descriptions make boundaries readable. Minor overlap exists between bridge_status and get_printer_attributes (both report 'status' at different layers), which could cause an occasional misselection.

    Naming Consistency4/5

    Strong snake_case verb_noun convention throughout (upload_file, list_jobs, get_job_status, cancel_job, delete_uploaded_file). The lone deviation is bridge_status, which puts the noun first instead of following the get_/list_ verb pattern.

    Tool Count5/5

    13 tools is well within the ideal range for a print-bridge server, with sensible coverage of uploads, jobs, and printer discovery. Each tool appears to earn its place; nothing looks redundant or padded.

    Completeness4/5

    Full lifecycle is covered for staged uploads (upload, list, get, delete) and jobs (list, status, cancel, submit via print_file), plus printer discovery and validation. Gaps remain around job control (hold/release/pause/resume) and any cleanup of expired jobs, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data