Skip to main content
Glama
bizswoop-development

bizprint-mcp-server

by bizswoop-development
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bizprint-mcp-server

No user-submitted related servers found.

    Related Servers

    • printagent

      huy97
      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.
      214 npm
      MIT

    • printbridge

      starkshtlm
      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

    • MCP 3D Printer Server

      mcpflow
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to connect Claude with various 3D printer management systems, allowing tasks like printer status monitoring, file management, print job control, and STL file manipulation.
      87 npm
      GPL 2.0

    • thermal-mcp

      EthanPany
      A
      license
      A
      quality
      A
      maintenance
      Print beautiful HTML & Markdown on a $30 thermal receipt printer, straight from your AI agent.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource (printer, print job, station) and action (create, get, list). There is no overlap; for example, create_print_job is clearly for creating jobs, while get_print_job and list_print_jobs retrieve existing jobs.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: create_print_job, get_printer, get_print_job, get_station, list_printers, list_print_jobs, list_stations. The pattern is uniform and predictable.

    Tool Count5/5

    With 7 tools, the server covers three core resources (printer, print job, station) with create, get, and list operations for each, which feels well-scoped and appropriate for a print management MCP server.

    Completeness4/5

    The server provides CRUD-like coverage for the main resources: create for print jobs, and read (get/list) for all three. Missing update and delete operations for printers and stations, but the core workflow of creating and tracking print jobs is complete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources