qr-cow MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QRCOW_API_BASE | No | Base URL for the qr-cow API (default: https://qr-cow.com/api) | https://qr-cow.com/api |
| QRCOW_API_TOKEN | Yes | Your qr-cow API token (starts with qrc_live_) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_qrcodeA | Create and SAVE a QR code in the customer's qr-cow account (it appears on their dashboard and is tracked). Pick a content type and pass the content as a string. Static codes are unlimited on every plan; dynamic codes (editable + scan analytics) have a per-plan limit (the free plan includes a few). To just render a styled image without saving, use render_styled_qrcode instead. |
| render_styled_qrcodeA | Render a fully STYLED QR code image (colours, dot + eye shapes, gradient, logo, error-correction) from data and a style, WITHOUT saving it to the account. Great for generating codes in bulk. Use a |
| list_qrcodesB | List the customer's recent QR codes, newest first. |
| get_qrcodeA | Fetch full details for one QR code by id, including current redirect URL for dynamic codes. |
| update_qrcode_destinationA | Update a dynamic QR code's destination URL. The printed code doesn't change — only what scanning it leads to. |
| delete_qrcodeA | Soft-delete a QR code. Scans afterwards return 404. |
| get_qrcode_analyticsA | Fetch scan analytics for one QR code: total scans, unique scanners, breakdown by country, device, and hour of day. |
| meA | Return the authenticated user's profile + plan info. |
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 8 tools
Each tool has a clearly distinct purpose. render_styled_qrcode is explicitly stateless and different from create_qrcode, while update_qrcode_destination, get_qrcode_analytics, and me serve unique roles without overlap.
Most tools follow a consistent verb_noun pattern (create_qrcode, list_qrcodes, get_qrcode, delete_qrcode, render_styled_qrcode, update_qrcode_destination, get_qrcode_analytics). The lone exception is 'me', which is a minor deviation in an otherwise predictable scheme.
With 8 tools, the server is well-scoped for a QR code management service. Each tool fulfills a necessary operation without redundancy or excessive granularity, fitting comfortably in the ideal 3-15 range.
The tool set covers the full QR code lifecycle: create, read, list, delete, update (destination), plus rendering without saving, analytics, and user plan info. No significant gaps are evident for the stated purpose.