memobird-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMOBIRD_AK | Yes | Your Memobird developer API Key (AK) from open.memobird.cn. | |
| MEMOBIRD_DEVICE_ID | Yes | Your Memobird device ID (memobirdID). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
咕咕机(Memobird)热敏打印机服务。可用工具:print_text 打印文本、print_image 打印图片、print_url 打印网页、print_mixed 图文混排、print_status 查询出纸状态。
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| print_textA | 把一段纯文本打印到咕咕机。 文本按 GBK 编码发送,emoji 和部分生僻字会被静默丢弃。 |
| print_imageA | 把一张图片打印到咕咕机。 图片会等比缩放到 384px 宽并转成黑白,细节多的图建议先用高对比度版本。 |
| print_urlA | 打印某个网页的内容(由咕咕机服务端抓取渲染)。 URL 必须公网可访问,内网地址、需要登录的页面打不出来。 |
| print_mixedB | 把文字和图片混排打印在同一张小票上。 |
| print_statusC | 查询一张小票是否已经出纸。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.