Skip to main content
Glama
Sign In
memobird-mcp

memobird-mcp

by lingchen-jiager
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to memobird-mcp

No user-submitted related servers found.

    Related Servers

    • Memobird MCP Server

      CafuChino
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Memobird thermal printers to print text, HTML, web pages, and images directly from MCP-enabled clients. It includes tools for device binding, image conversion, and monitoring print job status.
      7 npm
      1
      ISC

    • @inkrelay/mcp

      GauravBR
      A
      license
      Not graded
      quality
      C
      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

    • 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.
      22 npm
      MIT

    • bizprint-mcp-server

      bizswoop-development
      A
      license
      A
      quality
      D
      maintenance
      Connect AI agents to physical printers. Print receipts, shipping labels, and packing slips to your existing BizPrint-connected printers from Claude and other MCP clients.
      7
      1
      MIT

    • Memobird GT1 MCP Server

      5uX1a0ma0
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables direct local Bluetooth printing of text and images to a Memobird GT1 thermal printer without the official app or cloud services.
      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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    print_text, print_image, and print_url target clearly distinct content types, and print_mixed is differentiated by combining text and image on one receipt. The only mild overlap is that print_mixed could arguably subsume print_text/print_image, but the descriptions make the intended use of each clear.

    Naming Consistency4/5

    All five tools share a consistent 'print_' prefix with a noun suffix (text, image, url, mixed), which is highly predictable. print_status is a minor semantic deviation since it queries rather than prints, but the shared prefix keeps the set coherent.

    Tool Count5/5

    Five tools is well-scoped for a small printer device API: one per supported content type plus a status check. Each tool earns its place with no filler or redundancy.

    Completeness4/5

    The surface covers all plausible print payloads (text, image, URL, mixed) plus a job status check, so core workflows are covered. Minor gaps exist around device/online status and cancelling a queued receipt, which agents would have to work around.

    Resources