QR Branding
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QR_BRANDING_API_KEY | Yes | Your QR Branding API key. Keys look like `qrb_xxx...`. This npm MCP server always requires the API key. | |
| QR_BRANDING_API_BASE_URL | No | Override the gateway URL. Useful for self-hosters and staging. | https://qr-branding.com |
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 |
|---|---|
| qr_generateA | Generate a fully branded QR code with explicit control over colors, module/finder shapes, logo, caption, and output format. Use this when the user already knows the design they want. |
| qr_generate_aiA | Generate a QR code where the QR Branding LLM picks colors and shapes from a natural-language prompt. Best for "make me a luxury gold dotted QR for a coffee brand" style requests. |
| qr_list_templatesA | List the 118 pre-designed QR templates (id, name, description, preview thumbnail URL). Filter by category if the user asks for a specific style. |
| qr_generate_from_templateA | Render one of the curated templates by id, optionally overriding the encoded content, colors, or output format/size for this specific call. |
| qr_build_wifiA | Encode Wi-Fi credentials (SSID, password, auth type, hidden flag) into a scannable Wi-Fi QR. Returns both the WIFI:... payload string and a generated QR image. |
| qr_build_vcardA | Encode a contact card (vCard) with first and last name, organization, phone, email and website URL into a QR. Scanning the QR adds the contact to the phone's address book. |
| qr_build_geoA | Encode a latitude/longitude pair into a geo: URI QR. Scanning opens the location in the device's default maps app. |
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 7 tools
The three qr_generate* tools overlap in purpose (all produce a branded QR) but are cleanly separated by intent: manual control, AI-driven design, and template-based rendering, with descriptions that clarify when to pick each. The qr_build_wifi/vcard/geo tools are unmistakably distinct payload encoders.
All tools share a consistent qr_ prefix and snake_case, with a readable verb_noun structure (qr_generate, qr_list_templates, qr_build_wifi). Minor deviation is the mix of 'generate' vs 'build' verbs and the suffixed variants qr_generate_ai / qr_generate_from_template, but the pattern stays predictable.
Seven tools is well-scoped for a QR branding service, with each tool earning its place across generation modes, template discovery, and specific payload types. No redundant or filler tools.
The surface covers the full generation lifecycle (manual, AI, template), template listing, and three specialized payload builders. Minor gaps exist for other common encodings (URL, email, SMS, text) though qr_generate likely accepts arbitrary content, so agents can work around this.