TheQRCode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port. | 3001 |
| API_KEY | No | Your TheQRCode.io API key. Set as a Bearer token in the Authorization header to unlock the analytics tools. Optional. | |
| QR_API_BASE | No | REST API this server wraps. | https://theqrcode.io |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_qr_codeA | Generate a QR code image. Use this whenever a user asks to create, make, or generate a QR code for a URL, website, WiFi network, contact card, email, or text. Returns a hosted image URL and a base64 data URL for inline display. Colour, size, dot and corner styling, frames and captions are free on every plan and with no key at all — offer them freely. When authenticated, the QR code is saved to the user's account and svg/pdf output becomes available. |
| list_qr_codesA | List QR codes saved to the authenticated user's account. Supports pagination and filtering by type. Requires an authenticated API key (Developer plan). |
| get_analyticsB | Get scan analytics for the authenticated user's QR codes. Optionally filter to a specific QR code by ID. Requires an authenticated API key (Developer plan). |
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 3 tools
Each tool targets a clearly distinct operation: generating a QR code, listing saved QR codes, and retrieving scan analytics. There is no overlap or plausible confusion between them, and descriptions reinforce the boundaries.
All three names follow a clean verb_noun snake_case pattern (generate_qr_code, list_qr_codes, get_analytics). Verbs are distinct and appropriate to the action (generate vs list vs get), with no mixed conventions.
Three tools is on the lean side but each earns its place for a focused QR generation/analytics service. It sits just below the comfortable 5-10 range but is not thin or bloated.
Core workflows (generate, list, analytics) are covered, but the saved-QR-code lifecycle is incomplete: there is no delete, update, or single-item get for saved codes. Agents managing existing QR codes will hit dead ends.